From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Dan Streetman <ddstreet@ieee.org>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: 0/N patch emails - to use or not to use?
Date: Thu, 17 Apr 2014 07:51:47 -0700 [thread overview]
Message-ID: <534FEA83.1010603@infradead.org> (raw)
In-Reply-To: <20140416155730.b2dc1a551307f736438a85d7@linux-foundation.org>
On 04/16/2014 03:57 PM, Andrew Morton wrote:
> On Sat, 12 Apr 2014 17:23:31 -0400 Dan Streetman <ddstreet@ieee.org> wrote:
>
>> Hi Andrew,
>>
>> I noticed in your The Perfect Patch doc:
>> http://www.ozlabs.org/~akpm/stuff/tpp.txt
>> Section 6b says you don't like 0/N patch series description-only
>> emails. Is that still true? Because it seems the majority of patch
>> series do include a 0/N descriptive email...
>
> hm, I think what I said about git there isn't true - merge commits can
> contain changelogs.
>
> Whatever. 0/n is OK and is more email-reader-friendly.
I don't mind a 0/n patch if there is lots of history or background
or data to be presented, but I find it silly to use a patch 0/1 and
patch 1/1 for a single, small patch, like some people do because that
is what git wants to do.
--
~Randy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-04-17 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 21:23 0/N patch emails - to use or not to use? Dan Streetman
2014-04-16 22:57 ` Andrew Morton
2014-04-17 14:51 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=534FEA83.1010603@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).