[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6c5339f0808010823o434298ecn7b274c46fe857aba@mail.gmail.com>
Date: Fri, 1 Aug 2008 11:23:59 -0400
From: "Bob Copeland" <me@...copeland.com>
To: "Jiri Slaby" <jirislaby@...il.com>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
"Pekka Enberg" <penberg@...helsinki.fi>,
"Dave Young" <hidave.darkstar@...il.com>,
johannes@...solutions.net, tomasw@...il.com,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
ath5k-devel@...ema.h4ckr.net, linville@...driver.com,
stable@...nel.org
Subject: Re: [PATCH] ath5k : ath5k_config_interface deadlock fix
On Fri, Aug 1, 2008 at 11:02 AM, Jiri Slaby <jirislaby@...il.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?
--
Bob Copeland %% www.bobcopeland.com
--
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/
Powered by blists - more mailing lists