From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: describe fails on tagless branch
Date: Wed, 07 Feb 2007 02:19:20 +0100 [thread overview]
Message-ID: <45C92918.8010801@xs4all.nl> (raw)
In-Reply-To: <eqb73j$hri$1@sea.gmane.org>
Jakub Narebski escreveu:
>
> _Which_ INIT? In git there can be more than one root commit. In git.git
I don't really care, but I would like git-describe to produce something
useful in the absence of tags. The -g<SHA-1> already makes the commit
uniquely identifiable.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2007-02-07 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 0:23 describe fails on tagless branch Han-Wen Nienhuys
2007-02-07 0:40 ` Jakub Narebski
2007-02-07 1:19 ` Han-Wen Nienhuys [this message]
2007-02-07 2:14 ` Junio C Hamano
2007-02-07 9:08 ` Jakub Narebski
2007-02-07 9:22 ` Andy Parkins
2007-02-07 9:58 ` Junio C Hamano
2007-02-07 12:01 ` Andy Parkins
2007-02-07 12:37 ` Jakub Narebski
2007-02-07 16:29 ` 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=45C92918.8010801@xs4all.nl \
--to=hanwen@xs4all.nl \
--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).