From: Johannes Sixt <j.sixt@viscovery.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Joshua Shrader <jshrader83@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: can git-describe learn first-parent behavior?
Date: Tue, 21 Sep 2010 12:03:54 +0200 [thread overview]
Message-ID: <4C98830A.70203@viscovery.net> (raw)
In-Reply-To: <4C987C2E.3060001@drmicha.warpmail.net>
Am 9/21/2010 11:34, schrieb Michael J Gruber:
> The earlier tag (in terms of depth) wins, yes.
Does it? Then explain this result:
git describe e5498e8a^2 e5498e8a^1~24 e5498e8a
v1.7.0.7
v1.7.1.1
v1.7.1.1-38-ge5498e8
v1.7.1.1 is 25 commits away, while v1.7.0.7 is a parent (the second).
AFAICS, git-describe does The Right Thing (--first-parent).
-- Hannes
next prev parent reply other threads:[~2010-09-21 10:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 5:58 can git-describe learn first-parent behavior? Joshua Shrader
2010-09-21 9:34 ` Michael J Gruber
2010-09-21 9:35 ` [RFC PATCH] git-describe: introduce --first-parent Michael J Gruber
2010-09-21 10:03 ` Johannes Sixt [this message]
2010-09-21 11:49 ` can git-describe learn first-parent behavior? Michael J Gruber
2010-09-21 12:00 ` Johannes Sixt
2010-09-21 12:10 ` Michael J Gruber
2010-09-21 12:34 ` Johannes Sixt
2010-09-21 15:26 ` Michael J Gruber
2010-09-21 19:57 ` Joshua Shrader
2010-09-22 6:52 ` Michael J Gruber
2010-09-22 17:45 ` Joshua Shrader
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=4C98830A.70203@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jshrader83@gmail.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).