linux-kernel - Re: [PATCH 11/12] MAINTAINERS: Remove section WAVELAN NETWORK DRIVER & WIRELESS EXTENSIONS

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

Date:	Fri, 11 Jun 2010 13:17:50 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Joe Perches <joe@...ches.com>
Cc:	linux-kernel@...r.kernel.org, Jean Tourrilhes <jt@....hp.com>,
	Wolfram Sang <w.sang@...gutronix.de>
Subject: Re: [PATCH 11/12] MAINTAINERS: Remove section WAVELAN NETWORK
 DRIVER & WIRELESS EXTENSIONS

On Wed,  9 Jun 2010 12:38:37 -0700
Joe Perches <joe@...ches.com> wrote:

> commit 1d794e3b353b50ab5d9d46f7c15607f9ec8c78e0 removed it

grump.

Sentences start with capital letters and end with full-stops.

The preferred way of referring to a commit ID is

	1d794e3b353b50ab5d9d46f7c15607f9ec8c78e0 ("Staging: wavelan: delete the driver").

or

	1d794e3b353b ("Staging: wavelan: delete the driver").

Yes, it's a pita entering that in there, but I'd rather it be your pita
than my pita ;)

If someone can come up with a checkpatch rule which detects a git hash
not followed by ("text"), that would help.


Alternatively, we beat Linus up and just use bare commit ID's.  All
commit IDs refer to Linus's tree anwyay, so if someone wants to locate
a commit within a different tree, they look up the patch title in
Linus's tree first.

Except for when people send commit ID's which just don't exist in
Linus's tree, which happens occasionally.
--
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/