From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: describe fails on tagless branch
Date: Wed, 07 Feb 2007 01:40:51 +0100 [thread overview]
Message-ID: <eqb73j$hri$1@sea.gmane.org> (raw)
In-Reply-To: eqb660$ft7$1@sea.gmane.org
[Cc: git@vger.kernel.org]
Han-Wen Nienhuys wrote:
> try
>
> git init
> echo hoi > a
> git add a
> git commit -m 'add a' a
> git describe
>
> this yields
>
>
> [lilydev@haring t]$ git describe
> fatal: cannot describe '3b26396bbb5f18580ffd4bc31f70ef0738ec73d6'
>
>
> I would prefer it if an implicit tag INIT was supposed at the start of the
> history, so we'd get
>
> INIT-3b2...
_Which_ INIT? In git there can be more than one root commit. In git.git
repository mainline (maint, master, next and pu branches) has 4 roots
(plus three linear independent branches: man, html and todo, each with its
own root).
I agree that error description should probably be better: cannot describe
_why_.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-02-07 0:39 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 [this message]
2007-02-07 1:19 ` Han-Wen Nienhuys
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='eqb73j$hri$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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 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.