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 22:10:54 +0200
From:	Samuel Thibault <samuel.thibault@...-lyon.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.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

Sam Ravnborg, le Sat 21 Aug 2010 22:05:28 +0200, a écrit :
> The canonical patch subject line is:
> 
>     Subject: [PATCH 001/123] subsystem: summary phrase
> 
>   - The body of the explanation, which will be copied to the
>     permanent changelog to describe this patch.
> 
> That should do it. We cannot tell what should NOT be done.

Yes, but according to what is above, we need to repeat the subject,
else it won't be in the changelog.  Actually, this is probably where it
should be said 'do not repeat the subject, it will already be included'.

> If you use git then it is trivial to commit your changes and
> generate patches using "git format-patch ..."

That's just one case. See above for the general case.

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