lkml.org 
[lkml]   [2010]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [PATCH,TRIVIAL] Replace Configure with Enable in description of MAXSMP
On Sat, Aug 21, 2010 at 1:16 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Sat, Aug 21, 2010 at 1:05 PM, Sam Ravnborg <sam@ravnborg.org> wrote:
>>
>> The canonical patch message body contains the following:
>>
>>  - A "from" line specifying the patch author.
>
> Btw, git (and other systems, at least Andrew's patchqueue) also accepts
>
>  - a Subject: line [...]
>
>  - a "Date: " line [...]

So Arjan just sent out a patch that does all three. See

http://lkml.indiana.edu/hypermail/linux/kernel/1008.2/02557.html

for an example.

And note that all those three lines can be dropped. In the absence of
the small "fake email header" at the top of the email body, git (and
again: also other mail applicator tools like the ones Andrew uses)
will take the information from the real email headers. So putting them
in the body is by no means required, but in the body they do end up
being more likely to not be corrupted by further emailing.

It's also a way to fix up a broken email system, for example. Lots of
people have email accounts that screw up their names (interesting
utf-8 characters being turned into regular ascii - for Finns, 'ä'
might be turned into 'a' or 'ae', for example), or maybe you want to
use your work email in the kernel logs, but you're using your home
email to send out the patch etc.

So sometimes the "put the header info at the top of the body" works as
a way to fix up incorrect information in your email headers.

Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2010-08-21 22:31    [W:0.887 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site