netdev - Re: [GIT PULL 0/5] IEEE 802.15.4 last-minute fixes.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090804.090921.198630830.davem@davemloft.net>
Date:	Tue, 04 Aug 2009 09:09:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dbaryshkov@...il.com
Cc:	netdev@...r.kernel.org, slapin@...fans.org,
	linux-zigbee-devel@...ts.sourceforge.net
Subject: Re: [GIT PULL 0/5] IEEE 802.15.4 last-minute fixes.

From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Date: Tue, 4 Aug 2009 18:48:10 +0400

> On Tue, Aug 04, 2009 at 05:58:10AM -0700, David Miller wrote:
>> From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
>> Date: Tue, 4 Aug 2009 12:51:48 +0400
>> 
>> > Will you pull the serie if I'll remove those two patches? Documentation
>> > fix isn't that important, however I'd really ask to pull the remaining
>> > two patches.
>> 
>> Yes.
> 
> Pushed the updated branch. Please pull.

Please don't resubmit changes like this.  It screws up all the
nice tracking of every patch we do on patchwork for networking
changes.

Please make a formal, full, reposting of the patch series you want me
to apply.  That way they can be tracked in patchwork, and the patches
can be replied to and commented upon (and such comments tracked in
patchwork as well).

When I say I'm tossing someone's changes, that means if they resubmit
they have to really resubmit everything, the patch postings at all.
Don't short-cut it with just a GIT tree refresh and pull request.

Thank you.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html