git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: finding earliest tags descended from a given commit
Date: Fri, 26 Jan 2007 23:42:46 -0500	[thread overview]
Message-ID: <20070127044246.GC14205@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0701262022230.25027@woody.linux-foundation.org>

On Fri, Jan 26, 2007 at 08:34:15PM -0800, Linus Torvalds wrote:
> On Fri, 26 Jan 2007, J. Bruce Fields wrote:
> >
> > 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?
> 
> You can name any revision based on the set of tags you have with:
> 
> 	git name-rev --tags <sha1-of-commit>
> 
> which will try to find the "simplest" way to name something by following 
> one of your tags.

That's interesting, I hadn't noticed name-rev before you and Shawn
mentioned it.

It only finds one name, though. When I tried it just now on my
repository what it found was a tag I'd created for an experimental
version, which probably wouldn't be what I wanted.  (Though it might be,
in some situations.)

--b.

  reply	other threads:[~2007-01-27  4:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-27  4:06 finding earliest tags descended from a given commit J. Bruce Fields
2007-01-27  4:22 ` Shawn O. Pearce
2007-01-27  4:34 ` Linus Torvalds
2007-01-27  4:42   ` J. Bruce Fields [this message]
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=20070127044246.GC14205@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).