git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] git describe --first-parent
Date: Tue, 11 Sep 2012 15:51:50 +0200	[thread overview]
Message-ID: <cover.1347370970.git.git@drmicha.warpmail.net> (raw)

While "git describe" behaves as documented, the notion of "most recent tag"
is not really easy to grab, and it's not always the way you want to describe
a commit.

"--first-parent" is the option which answers the question: Which is the
most recent tag on this branch which can be reached from this commit?
("This branch" being defined as "--first-parent" walk.)

I had suggested this before, but the discussion veered off quite a bit:
http://permalink.gmane.org/gmane.comp.version-control.git/156811

No need to discuss the way "git describe" behaves again ;)

Michael J Gruber (2):
  git-describe: introduce --first-parent
  describe: document and test --first-parent

 Documentation/git-describe.txt | 16 +++++++++++++++-
 builtin/describe.c             |  8 +++++++-
 t/t6120-describe.sh            |  7 +++++++
 3 files changed, 29 insertions(+), 2 deletions(-)

-- 
1.7.12.463.gbd9d638

             reply	other threads:[~2012-09-11 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 13:51 Michael J Gruber [this message]
2012-09-11 13:51 ` [PATCH 1/2] git-describe: introduce --first-parent Michael J Gruber
2012-09-11 16:41   ` Junio C Hamano
2012-09-11 13:51 ` [PATCH 2/2] describe: document and test --first-parent Michael J Gruber
2012-09-11 17:20   ` Junio C Hamano
2012-09-11 16:10 ` [PATCH 0/2] git describe --first-parent 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=cover.1347370970.git.git@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --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).