From: "J. Bruce Fields" <bfields@fieldses.org>
To: git@vger.kernel.org
Subject: finding earliest tags descended from a given commit
Date: Fri, 26 Jan 2007 23:06:18 -0500 [thread overview]
Message-ID: <20070127040618.GA14205@fieldses.org> (raw)
Just curious: every now and then somebody will ask me what kernel
version they need to upgrade to to get some given fix. I can find the
commit with the given fix easily enough. How do I then find the
earliest tagged version containing that fix?
More generally, given a commit, is there a quick way to find the set of
tags which tag commits descended from the given commit? Or to get the
subset of such tags which are earliest (in the sense that they're not
descendants of any of the others)?
I usually just do
git-describe <commit>
to make a guess, then
git log <tag>..<commit>
to verify, but perhaps there's something more clever, or something that
would work better in a project where the tags aren't necessarily all in
a straight line.
--b.
next reply other threads:[~2007-01-27 4:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 4:06 J. Bruce Fields [this message]
2007-01-27 4:22 ` finding earliest tags descended from a given commit Shawn O. Pearce
2007-01-27 4:34 ` Linus Torvalds
2007-01-27 4:42 ` J. Bruce Fields
2007-01-27 4:55 ` Shawn O. Pearce
2007-01-27 5:23 ` Junio C Hamano
2007-01-27 12:39 ` [PATCH] name-rev: introduce the --ref-filter=<regex> option Johannes Schindelin
2007-02-17 14:02 ` Johannes Schindelin
2007-02-17 14:59 ` Jeff King
2007-02-17 17:50 ` Johannes Schindelin
2007-02-17 18:25 ` Junio C Hamano
2007-02-17 23:13 ` [PATCH] git-name-rev: accept list of refs from user Jeff King
2007-02-17 23:19 ` Jeff King
2007-02-17 23:30 ` Junio C Hamano
2007-02-17 23:40 ` Jeff King
2007-02-18 0:02 ` Johannes Schindelin
2007-02-17 17:42 ` [PATCH] name-rev: introduce the --ref-filter=<regex> option Junio C Hamano
2007-02-17 18:01 ` Johannes Schindelin
2007-02-17 18:22 ` [PATCH] name-rev: introduce the --ref-filter=<pattern> option Johannes Schindelin
2007-02-17 18:47 ` Junio C Hamano
2007-02-17 23:55 ` Johannes Schindelin
2007-02-17 19:00 ` Junio C Hamano
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=20070127040618.GA14205@fieldses.org \
--to=bfields@fieldses.org \
--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.
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).