From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Bob Copeland <me@bobcopeland.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
tomasw@gmail.com, Dave Young <hidave.darkstar@gmail.com>,
stable@kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, linville@tuxdriver.com,
Pekka Enberg <penberg@cs.helsinki.fi>,
ath5k-devel@venema.h4ckr.net, johannes@sipsolutions.net,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [ath5k-devel] [PATCH] ath5k : ath5k_config_interface deadlock fix
Date: Fri, 01 Aug 2008 17:28:14 +0100 [thread overview]
Message-ID: <4893399E.8080503@tuffmail.co.uk> (raw)
In-Reply-To: <b6c5339f0808010823o434298ecn7b274c46fe857aba@mail.gmail.com>
Bob Copeland wrote:
> On Fri, Aug 1, 2008 at 11:02 AM, Jiri Slaby <jirislaby@gmail.com> wrote:
>
>>> Not to worry, the commit that introduced it was
>>> 9d139c810a2aa17365cc548d0cd2a189d8433c65, which as far as I can tell
>>> came in after 2.6.26.
>>>
>> git-describe 9d139c810a2aa17365cc548d0cd2a189d8433c65
>> v2.6.26-rc8-1219-g9d139c8
>>
>
> I'm not that expert in git, what does that mean? Some other commits
> for 2.6.27 also show a 2.6.26-rc from git-describe (e.g. my
> 3a078876caee).
>
> For my own investigation, I did a 'git-checkout v2.6.26' and looked at
> the code to see the patch had not been applied yet. Is there an
> easier way to definitively say commit X is/is not in tagged release Y?
>
>
Aha! I think we want git-describe --contains.
$ git-describe --contains 2b142900784c6e38c8d39fa57d5f95ef08e735d8
v2.6.27-rc1~55^2~1
Alan
next prev parent reply other threads:[~2008-08-01 16:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 7:46 [PATCH] ath5k : ath5k_config_interface deadlock fix Dave Young
2008-08-01 7:46 ` Dave Young
2008-08-01 8:01 ` Jiri Slaby
2008-08-01 8:01 ` Jiri Slaby
2008-08-01 8:03 ` Pekka Enberg
2008-08-01 8:03 ` Pekka Enberg
2008-08-01 8:14 ` Andrew Morton
2008-08-01 13:43 ` Bob Copeland
2008-08-01 15:02 ` Jiri Slaby
2008-08-01 15:21 ` Jiri Slaby
2008-08-01 15:21 ` [ath5k-devel] " Alan Jenkins
2008-08-01 15:25 ` git-describe [Was: ath5k_config_interface deadlock fix] Jiri Slaby
2008-08-01 16:11 ` Alan Jenkins
2008-08-01 15:23 ` [PATCH] ath5k : ath5k_config_interface deadlock fix Bob Copeland
2008-08-01 16:28 ` Alan Jenkins [this message]
2008-08-04 3:02 ` Dave Young
2008-08-04 8:06 ` Jiri Slaby
2008-08-04 9:02 ` Dave Young
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=4893399E.8080503@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=akpm@linux-foundation.org \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=hidave.darkstar@gmail.com \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.com \
--cc=penberg@cs.helsinki.fi \
--cc=stable@kernel.org \
--cc=tomasw@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.