Re: git describe origin ?
Hi,
On 7/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 16 quoted lines
> On Sat, 7 Jul 2007, Francis Moreau wrote:
>
> > 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/.
nope I'm not. I'll do read it thanks.
Show 14 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/dummy': unable to chdir or not a git archive
> > fatal: The remote end hung up unexpectedly
> > ls-remote --heads /tmp/dummy: command returned error: 1
> >
> > Maybe the output could be improved to be more readable.
>
> The first line is very helpful IMHO:
>
> fatal: '/tmp/dummy': unable to chdir or not a git archive
>
yep but the 2 others are just noise, aren't they ?
BTW, shouldn't "git remote add" have complained at first ?
thanks
--
Francis