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  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:	Sun, 16 Dec 2007 14:29:15 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Miller <davem@...emloft.net>
Cc:	shemminger@...ux-foundation.org, netdev@...r.kernel.org,
	bugme-daemon@...zilla.kernel.org, berrange@...hat.com,
	jeff@...zik.org, herbert@...dor.apana.org.au, rjw@...k.pl
Subject: Re: [PATCH] bridge: assign random address

On Sun, 16 Dec 2007 13:37:17 -0800 (PST) David Miller <davem@...emloft.net> wrote:

> From: Stephen Hemminger <shemminger@...ux-foundation.org>
> Date: Tue, 11 Dec 2007 15:48:35 -0800
> 
> > Subject: Re: [PATCH] bridge: assign random address
> 
> "bridge" should all-caps and in brackets,

No, "bridge" should not be in [].  Lots of people's patch-receiving scripts
assume that any text in [] is to be removed as the patch is committed.  It
contains text which is only relevant to the particular email which carried
the patch.  Stuff like "patch" and "4/5" and "linux-2.6.23", etc.

> "assign random address"
> should be capitalized like a proper english sentence with a period at
> the end.

Actually I usually remove the caps and the waste-of-space period, but
that's much less important than the brackets abuse.  The bracket convention
is quite useful and I've often wondered why I need to edit the patch title
when I merge up patches from net developers ;)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists