From: Theodore Tso <tytso@mit.edu>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: I just pulled and built 'next'...
Date: Tue, 9 Jan 2007 08:54:01 -0500 [thread overview]
Message-ID: <20070109135401.GB17352@thunk.org> (raw)
In-Reply-To: <20070109032124.GA1904@spearce.org>
On Mon, Jan 08, 2007 at 10:21:24PM -0500, Shawn O. Pearce wrote:
> So what about doing Junio's suggestion of going by topology and
> coming up with the possible set of tags (v1.5.0-rc0 and v1.4.4.4
> right now), and if more than one is found compute the number of
> commits between each tag and the requested revision, and take the
> tag that has a smallest number of commits?
Ah, thanks for showing the example using git-rev-list. I was assuming
"topology" based on the distance as shown by gitk, and that's quite
different from what git-rev-list shows. Agreed, that hueristic makes
a lot of sense.
- Ted
next prev parent reply other threads:[~2007-01-09 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 13:32 I just pulled and built 'next' Theodore Ts'o
2007-01-08 20:11 ` Junio C Hamano
2007-01-08 21:00 ` Theodore Tso
2007-01-09 3:21 ` Shawn O. Pearce
2007-01-09 9:39 ` Andreas Ericsson
2007-01-09 13:54 ` Theodore Tso [this message]
2007-01-09 17:35 ` Uwe Kleine-König
2007-01-10 0:06 ` Shawn O. Pearce
2007-01-10 13:24 ` Uwe Kleine-Koenig
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=20070109135401.GB17352@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.