git describe origin ?

git describe origin ?

[Francis Moreau]

Hi,

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

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.

Thanks
-- 
Francis

Re: git describe origin ?

[Johannes Schindelin]

Hi,

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/.

> 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

Re: git describe origin ?

[Francis Moreau]

Hi,

On 7/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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.

>
> > 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

Re: git describe origin ?

[Johannes Schindelin]

Hi,

On Sat, 7 Jul 2007, Francis Moreau wrote:

> On 7/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Sat, 7 Jul 2007, Francis Moreau wrote:
> > 
> > > 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 ?

There are actually four programs involved, it seems. You get an error 
message from all except "git remote".

> BTW, shouldn't "git remote add" have complained at first ?

No. Sometimes the URL is not yet available, yet, you want to add it for 
later reference (think bundles). Sometimes you are simply offline.

Ciao,
Dscho

Re: git describe origin ?

[Francis Moreau]

On 7/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> No. Sometimes the URL is not yet available, yet, you want to add it for
> later reference (think bundles). Sometimes you are simply offline.
>

true.

-- 
Francis

Re: git describe origin ?

[Francis Moreau]

On 7/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> 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/.
>

Ok I took a look to it and I think I get the idea. But now I don't
understand this example taken from "git-branch" documentation:

"""
Delete unneeded branch

    $ git clone git://git.kernel.org/.../git.git my.git
    $ cd my.git
    $ git branch -d -r todo html man   (1)
"""

I think the last command can't work since the given refs can't be
found according the rules given by the documention you mentioned
earlier.

thanks
-- 
Francis