From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: name-rev does not show the shortest path
Date: Thu, 23 Aug 2007 12:38:17 +0200 [thread overview]
Message-ID: <20070823103817.GF6573@informatik.uni-freiburg.de> (raw)
Hello,
I want to check to which kernel version I need to upgrade to get a
certain feature. For my case it was introduced in 0567a0c022d5b.
zeisberg@cassiopeia:~/gsrc/linux-2.6$ rev=0567a0c022d5b343370a343121f38fd89925de55
zeisberg@cassiopeia:~/gsrc/linux-2.6$ git name-rev --tags $rev
0567a0c022d5b343370a343121f38fd89925de55 tags/v2.6.22~1686^2~1^3~5
zeisberg@cassiopeia:~/gsrc/linux-2.6$ git name-rev --refs=*-rc1 $rev
0567a0c022d5b343370a343121f38fd89925de55 tags/v2.6.22-rc1~1009^2~1^3~5
I don't now the underlaying algorithm, maybe it's to get a short string?
Anyhow I want to know the earliest tag that includes this patch? Is
there something I missed?
I remember there was a similar discussion regarding describe.
BTW: gitk does the right thing, it says:
Follows: v2.6.21-rc7
Precedes: v2.6.22-rc1
(called with
zeisberg@cassiopeia:~/gsrc/linux-2.6$ gitk 0567a0c022d5b343370a343121f38fd89925de55^..0567a0c022d5b343370a343121f38fd89925de55
)
I didn't check how it does that though.
Best regards
Uwe
--
Uwe Kleine-König
exit vi, lesson I:
: q ! <CR>
next reply other threads:[~2007-08-23 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 10:38 Uwe Kleine-König [this message]
2007-08-24 11:55 ` name-rev does not show the shortest path Julian Phillips
2007-08-24 12:52 ` Uwe Kleine-König
2007-08-24 15:21 ` Julian Phillips
2007-08-24 18:33 ` Junio C Hamano
2007-08-25 15:04 ` Johannes Schindelin
2007-08-26 9:23 ` Jeff King
2007-08-26 15:38 ` Johannes Schindelin
2007-08-27 9:24 ` Jeff King
2007-08-27 9:57 ` Johannes Schindelin
2007-08-27 11:18 ` Johannes Schindelin
2007-08-27 11:37 ` [PATCH] name-rev: Fix non-shortest description Johannes Schindelin
2007-08-27 19:27 ` Uwe Kleine-König
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070823103817.GF6573@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).