public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Jean Tourrilhes <jt@hpl.hp.com>,
	Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: [PATCH 11/12] MAINTAINERS: Remove section WAVELAN NETWORK DRIVER & WIRELESS EXTENSIONS
Date: Fri, 11 Jun 2010 13:17:50 -0700	[thread overview]
Message-ID: <20100611131750.6c62691a.akpm@linux-foundation.org> (raw)
In-Reply-To: <0f7d3ebb9e9e01b87c00fc3061861f2172ea790d.1276112118.git.joe@perches.com>

On Wed,  9 Jun 2010 12:38:37 -0700
Joe Perches <joe@perches.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.

  reply	other threads:[~2010-06-11 20:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 19:38 [PATCH 00/12] MAINTAINERS: Cleanups after renames/deletions Joe Perches
2010-06-09 19:38 ` [PATCH 01/12] MAINTAINERS: Update ARM/BCMRING MTD NAND DRIVER file patterns Joe Perches
2010-06-09 19:38 ` [PATCH 02/12] MAINTAINERS: Update ARM/NUVOTON W90X900 ARM ARCHITECTURE " Joe Perches
2010-06-10  1:47   ` Wan ZongShun
2010-06-10  1:55     ` Joe Perches
2010-06-09 19:38 ` [PATCH 03/12] MAINTAINERS: Update ARM/VOIPAC PXA270 " Joe Perches
2010-06-09 19:45   ` Marek Vasut
2010-06-09 19:38 ` [PATCH 04/12] MAINTAINERS: Update ARM/ZIPIT Z2 SUPPORT " Joe Perches
2010-06-09 19:38 ` [PATCH 05/12] MAINTAINERS: Update NETWORKING [WIRELESS] " Joe Perches
2010-06-09 19:38 ` [PATCH 06/12] MAINTAINERS: Update PPP OVER L2TP " Joe Perches
2010-06-09 19:38 ` [PATCH 07/12] MAINTAINERS: Update RICOH SMARTMEDIA/XD DRIVER " Joe Perches
2010-06-09 19:38 ` [PATCH 08/12] MAINTAINERS: Remove section SMX UIO Interface Joe Perches
2010-06-09 22:32   ` Hans J. Koch
2010-06-09 22:51   ` Ben Nizette
2010-06-09 19:38 ` [PATCH 09/12] MAINTAINERS: Update SPEAR CLOCK FRAMEWORK SUPPORT file patterns Joe Perches
2010-06-09 19:38 ` [PATCH 10/12] MAINTAINERS: Remove section STRIP Joe Perches
2010-06-09 19:38 ` [PATCH 11/12] MAINTAINERS: Remove section WAVELAN NETWORK DRIVER & WIRELESS EXTENSIONS Joe Perches
2010-06-11 20:17   ` Andrew Morton [this message]
2010-06-09 19:38 ` [PATCH 12/12] Documentation/networking/wavelan.txt: Deleted, not in tree Joe Perches
2010-06-09 19:51   ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100611131750.6c62691a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w.sang@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox