[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110413103144.GB3066@iram.es>
Date: Wed, 13 Apr 2011 12:31:44 +0200
From: Gabriel Paubert <paubert@...m.es>
To: Andreas Schwab <schwab@...hat.com>
Cc: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, Greg KH <greg@...ah.com>,
linuxppc-dev@...ts.ozlabs.org, dri-devel@...ts.freedesktop.org,
LKML <linux-kernel@...r.kernel.org>,
Dave Airlie <airlied@...il.com>
Subject: Re: small git lesson [Was: Re: Revert
737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?]
On Wed, Apr 13, 2011 at 10:59:14AM +0200, Andreas Schwab wrote:
> Uwe Kleine-König <u.kleine-koenig@...gutronix.de> writes:
>
> > $ git name-rev --refs=refs/tags/v2.6\* 69a07f0b117a40fcc1a479358d8e1f41793617f2
> > 69a07f0b117a40fcc1a479358d8e1f41793617f2 tags/v2.6.39-rc2~3^2~43^2~4
> >
> > so it was introduced just before -rc2.
>
> $ git tag --contains 69a07f0b117a40fcc1a479358d8e1f41793617f2
> v2.6.39-rc1
> v2.6.39-rc2
>
So who is right? I think it was before rc1.
Anyway I'm aware that there are other git commands, although for the option
details I often have to have a look at the man page.
However in this case the main reason to fire gitk was to have a quick look
at the patch and its context, and simply reported the "Precedes" line
in the display, which is 2.6.39-rc1. It also follow v2.6.37-rc2, which means
that it has been quite a long time outside the main tree.
Gabriel
--
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