# git describe origin ? 6 messages from 2007-07-07 to 2007-07-08. Participants: Francis Moreau, Johannes Schindelin. Thread: https://gitlist.dev/t/8916 ## Francis Moreau, 2007-07-07 15:51 Subject: git describe origin ? Message-ID: <38b2ab8a0707070851m25d615bdn4f7286cbadaf1316@mail.gmail.com> URL: https://gitlist.dev/e/38b2ab8a0707070851m25d615bdn4f7286cbadaf1316%40mail.gmail.com ``` 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 ``` ## Johannes Schindelin, 2007-07-07 16:33 Subject: Re: git describe origin ? Message-ID: URL: https://gitlist.dev/e/Pine.LNX.4.64.0707071728330.4093%40racer.site In-Reply-To: <38b2ab8a0707070851m25d615bdn4f7286cbadaf1316@mail.gmail.com> ``` 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 ``` ## Francis Moreau, 2007-07-07 16:53 Subject: Re: git describe origin ? Message-ID: <38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@mail.gmail.com> URL: https://gitlist.dev/e/38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb%40mail.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 ``` ## Johannes Schindelin, 2007-07-07 17:14 Subject: Re: git describe origin ? Message-ID: URL: https://gitlist.dev/e/Pine.LNX.4.64.0707071812570.4093%40racer.site In-Reply-To: <38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@mail.gmail.com> ``` Hi, On Sat, 7 Jul 2007, Francis Moreau wrote: > On 7/7/07, Johannes Schindelin 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 ``` ## Francis Moreau, 2007-07-07 17:27 Subject: Re: git describe origin ? Message-ID: <38b2ab8a0707071027v229b127bq89c56eff5a6cd54f@mail.gmail.com> URL: https://gitlist.dev/e/38b2ab8a0707071027v229b127bq89c56eff5a6cd54f%40mail.gmail.com In-Reply-To: ``` On 7/7/07, Johannes Schindelin 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 ``` ## Francis Moreau, 2007-07-08 13:51 Subject: Re: git describe origin ? Message-ID: <38b2ab8a0707080651m2242b518x5313e852621db2cf@mail.gmail.com> URL: https://gitlist.dev/e/38b2ab8a0707080651m2242b518x5313e852621db2cf%40mail.gmail.com In-Reply-To: ``` 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/. > 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 ```