From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Andreas Schwab <schwab@redhat.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: small git lesson [Was: Re: Revert 737a3bb9416ce2a7c7a4170852473a4fcc9c67e8 ?]
Date: Wed, 13 Apr 2011 11:36:08 +0200 [thread overview]
Message-ID: <20110413093608.GO18850@pengutronix.de> (raw)
In-Reply-To: <m339lm8r31.fsf@redhat.com>
Hello,
On Wed, Apr 13, 2011 at 10:59:14AM +0200, Andreas Schwab wrote:
> Uwe Kleine-König <u.kleine-koenig@pengutronix.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
huh, I thought git name-rev prefers old[1] refs (similar to describe
prefering newer).
$ for rc in 1 2; do git name-rev --refs=refs/tags/v2.6.39-rc$rc 69a07f0b1; done
69a07f0b1 tags/v2.6.39-rc1~79^2~31^2~4
69a07f0b1 tags/v2.6.39-rc2~3^2~43^2~4
I would prefer the v2.6.39-rc1 name even though it's nearer[1] at
v2.6.39-rc2.
If it should stay as is, what is the best way to find out the oldest
tag?
Best regards
Uwe
[1] as in minimizing
git rev-list 69a07f0b117a..$ref | wc -l
(v2.6.39-rc1 -> 21281; v2.6.39-rc2 -> 21608)
[2] as in minimizing the number of traversing a parent link.
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
parent reply other threads:[~2011-04-13 9:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m339lm8r31.fsf@redhat.com>]
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=20110413093608.GO18850@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=schwab@redhat.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 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).