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]
Message-ID: <AANLkTimcKkkRUSHOKo89ufZ4JfexsgKhUTHNroZqWH7_@mail.gmail.com>
Date:	Fri, 25 Feb 2011 08:54:17 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Sergei Shtylyov <sshtylyov@...sta.com>
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Nicolas Pitre <nicolas.pitre@...aro.org>,
	Russell King <linux@....linux.org.uk>
Subject: Re: [PATCH v4 6/7] arm/dt: Basic tegra devicetree support

On Fri, Feb 25, 2011 at 6:30 AM, Sergei Shtylyov <sshtylyov@...sta.com> wrote:
> On 24-02-2011 0:36, Grant Likely wrote:
>>>> v2: Fixed cut-and-paste error in commit text
>
>>>    Shouldn't this sentence follow the --- tearline?
>
>> Nope!  It is actually quite useful for the version information to show
>> up in the commit text.  That way you know *exactly* which version got
>> merged.  dwmw2 pointed that out to me a few months back.
>
>   Well, I think that depends on the patch. If you have say 9 revisions with
> significant changes (that's what I actually had) and the revision history
> far exceeds the original patch description, then this will just become too
> ugly I think...

Meh.  commit text is cheap and useful.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ