Re: git describe origin ?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 7, 2007, 16:33 UTC
Message-ID: <Pine.LNX.4.64.0707071728330.4093@racer.site>
In-Reply-To: <38b2ab8a0707070851m25d615bdn4f7286cbadaf1316@mail.gmail.com>

Hi,

On Sat, 7 Jul 2007, Francis Moreau wrote:

Show 6 quoted lines

> I was wondering what does 'git describe origin' command mean on a git
> repo. Does it mean ?
> 
>    a/ git describe origin/HEAD
>    b/ git describe origin/master
>    c/ something else

This is completely unrelated to "git describe". It is about naming commits AKA "specifying revisions". You might find the section "SPECIFYING REVISIONS" in Documentation/git-rev-parse.txt especially helpful. FWIW this section is hinted at in the section "Symbolic Identifiers" in Documentation/git.txt.

If you're too lazy to read, it's a/.

Show 8 quoted lines

> I also played with git remote and did something silly like: 
> $ git remote add bob /tmp/dummy # dummy does not exist
> $ git remote show bob
> fatal: '/tmp/toto': unable to chdir or not a git archive
> fatal: The remote end hung up unexpectedly
> ls-remote --heads /tmp/toto: command returned error: 1
> 
> Maybe the output could be improved to be more readable.

The first line is very helpful IMHO:

	fatal: '/tmp/toto': unable to chdir or not a git archive

Ciao, Dscho