From: Mark Burton <markb@ordern.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Git describe question
Date: Mon, 14 Jul 2008 09:20:40 +0100 [thread overview]
Message-ID: <20080714092040.4090046b@crow> (raw)
In-Reply-To: <7vvdz8hp3d.fsf@gitster.siamese.dyndns.org>
Thanks for the speedy response.
> A longer answer. v1.5.6.X releases are from 'maint'. The branch has
> forked from the mainline loooong time ago (at v1.5.6, to be exact), and
> has only fixes. 'master' is a separate branch for development that would
> eventually lead to the next major release (planned to be v1.6.0).
Ok, I understand what it's doing now - but that makes me wonder if it
would be useful/possible to be able to specify that git describe only
considers the commits on top of the tag for the current (or some
specified branch). i.e. at the moment, gitk shows 8 commits on top of
v1.5.6.3 in the master branch.
As the master branch is the checked out branch and the v1.5.6.3 tag
tags a commit in that branch (via the merge) is it not possible to only
consider the commits between the tag and the HEAD on that branch?
Sorry, I don't understand the git internals (yet) so I don't know if
this is a stupid question and I am certainly not in a position to try
and implement it myself (yet).
Cheers,
Mark
next prev parent reply other threads:[~2008-07-14 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 7:55 Git describe question Mark Burton
2008-07-14 8:00 ` Junio C Hamano
2008-07-14 8:20 ` Mark Burton [this message]
2008-07-14 22:29 ` Jean-Luc Herren
2008-07-14 23:17 ` Junio C Hamano
2008-07-15 6:40 ` Mark Burton
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=20080714092040.4090046b@crow \
--to=markb@ordern.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.