linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jirislaby@gmail.com
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@mkarcher.dialup.fu-berlin.de
Subject: Re: ath5k text
Date: Mon, 18 Aug 2008 00:05:13 -0700 (PDT)	[thread overview]
Message-ID: <20080818.000513.224752343.davem@davemloft.net> (raw)
In-Reply-To: <48A91E12.1060901@gmail.com>

From: Jiri Slaby <jirislaby@gmail.com>
Date: Mon, 18 Aug 2008 09:00:34 +0200

> On 08/18/2008 12:12 AM, David Miller wrote:
> > Their commit messages reference SHA IDs but do not give a commit
> > header line text reference as well.
> > 
> >       ath5k: Don't fiddle with MSI on suspend/resume.
> 
> John, this is it (even if I don't understand the purpose):

The purpose is that when patches are backported or moved to
other GIT trees, the SHA ID is going to be different.

So when you reference just the SHA ID it is not enough
infomration to universally find the commit you are referring
to.

Do you understand "the purpose" now? :-)


  reply	other threads:[~2008-08-18  7:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 18:56 pull request: wireless-2.6 2008-08-17 John W. Linville
2008-08-17 22:12 ` David Miller
2008-08-18  0:23   ` Larry Finger
2008-08-18  7:00   ` ath5k text [Was: pull request: wireless-2.6 2008-08-17] Jiri Slaby
2008-08-18  7:05     ` David Miller [this message]
2008-08-18 15:15   ` pull request: wireless-2.6 2008-08-18 John W. Linville
2008-08-19  4:16     ` David Miller
2008-08-19  4:27       ` Stephen Rothwell
2008-08-19  4:29         ` David Miller

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=20080818.000513.224752343.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jirislaby@gmail.com \
    --cc=kernel@mkarcher.dialup.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).