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:05:28 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>,
	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

> 
> Ah, I didn't realize you scripts include the subject topic too. Maybe it
> should be said in SubmittingPatches that the "summary phrase" shouldn't
> be repeated in the body.

>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.

  - An empty line.

  - The body of the explanation, which will be copied to the
    permanent changelog to describe this patch.

  - The "Signed-off-by:" lines, described above, which will
    also go in the changelog.

  - A marker line containing simply "---".

  - Any additional comments not suitable for the changelog.

  - The actual patch (diff output).

That should do it. We cannot tell what should NOT be done.

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

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