Re: 0/N patch emails - to use or not to use?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/16/2014 03:57 PM, Andrew Morton wrote:
> On Sat, 12 Apr 2014 17:23:31 -0400 Dan Streetman <ddstreet@xxxxxxxx> 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@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]