From: Francis Moreau Date: Sat, 07 Jul 2007 16:53:52 GMT Subject: Re: git describe origin ? Message-ID: <38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@mail.gmail.com> In-Reply-To: Hi, On 7/7/07, Johannes Schindelin 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