linux-kernel - Re: [PATCH,TRIVIAL] Replace Configure with Enable in description of MAXSMP

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] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 21 Aug 2010 13:16:48 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Samuel Thibault <samuel.thibault@...-lyon.org>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	Nick Piggin <npiggin@...nel.dk>
Subject: Re: [PATCH,TRIVIAL] Replace Configure with Enable in description of MAXSMP

On Sat, Aug 21, 2010 at 1:05 PM, Sam Ravnborg <sam@...nborg.org> wrote:
>
> From said document:
> 15) The canonical patch format
>
> The canonical patch subject line is:
>
>    Subject: [PATCH 001/123] subsystem: summary phrase
>
> 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 to repeat the subject. This can be useful if you
(for example) want to keep the actual email subject in an old thread,
and thus want to override the email Subject: line with one that is
appropriate for the patch itself.

 - a "Date: " line to specify the date of the patch. Not that most
people care, but when patches get forwarded by email and sign-off's
added, the date of the newer email will obviously change. So _if_ you
care about the date when you actually sent out the patch, you can add
the Date: line to specify the date of the submission, and then as
people forward it, that one may stay around (because it is in the body
of the email)

Quite frankly, I don't personally much care for the "date" line, and
it easily gets lost if a patch is maintained not in email, but in some
other patch queue system (so I think the date line gets dropped if the
patch goes through Andrew, for example). But a patch queue that
doesn't honor the summary and author information isn't a patch queue,
it's a broken mess.

Putting the author line ("From: xyz <abc@...mple.com>") at the top of
the email body is always a good idea, though. That means that other
people can forward the email, without accidentally then becoming
marked as the author. Of course, careful people will make sure to save
authorship anyway, but mistakes have happened.

(Of course, if you send the patch directly to me or Andrew, you don't
really need to. We both make sure that author information gets saved
off. It tends to be people who aren't quite as used to emailed patches
that get this wrong).

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