netdev - Re: [PATCH] fix IBM EMAC driver after rename.

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 18 Aug 2011 21:09:58 -0700
From:	Joe Perches <joe@...ches.com>
To:	Tony Breeds <tony@...eyournoodle.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	jeffrey.t.kirsher@...el.com
Subject: Re: [PATCH] fix IBM EMAC driver after rename.

On Fri, 2011-08-19 at 13:57 +1000, Tony Breeds wrote:
> On Thu, Aug 18, 2011 at 08:44:00PM -0700, David Miller wrote:
> > Don't do this :-(  When you reply to me as your new version of the patch
> > it craps up the commit message.
> > Always make a fresh, new, patch posting with a clean full commit message
> > without any non-essential material included.
> > I'm not applying this, because I'm pretty sick and tired of having to
> > edit up people's patch postings when they do stuff like this.
> Sorry I thought git am coped with this.

It can if you move the quoted stuff below the
---
separator, though I don't know what patchworks
does with threaded [PATCH V2] content.  I do
think it's useful when the corrected patch
is appropriately threaded.

The corrected patch email could look like:

Subject: [PATCH V2] module: description

typical multi-line patch description...

Signed-off-by: etc

---

> On some date, somebody wrote:
> quoted stuff

Description of delta between patch 1 and patch 2.

actual patch...


--
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