{"thread":{"id":"8916","subject":"git describe origin ?","startedAt":"2007-07-07T15:51:58Z","lastAt":"2007-07-08T13:51:20Z","messageCount":6,"participants":["Francis Moreau","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"46691","messageId":"38b2ab8a0707070851m25d615bdn4f7286cbadaf1316@mail.gmail.com","threadId":"8916","inReplyTo":null,"subject":"git describe origin ?","fromName":"Francis Moreau","fromEmail":"francis.moro@gmail.com","sentAt":"2007-07-07T15:51:58Z","receivedAt":"2007-07-07T15:51:58Z","isPatch":false,"sender":{"key":"francis.moro@gmail.com","avatar":null},"body":"Hi,\n\nI was wondering what does 'git describe origin' command mean on a git\nrepo. Does it mean ?\n\n a/ git describe origin/HEAD\n b/ git describe origin/master\n c/ something else\n\nI also played with git remote and did something silly like:\n\n$ git remote add bob /tmp/dummy # dummy does not exist\n$ git remote show bob\nfatal: '/tmp/toto': unable to chdir or not a git archive\nfatal: The remote end hung up unexpectedly\nls-remote --heads /tmp/toto: command returned error: 1\n\nMaybe the output could be improved to be more readable.\n\nThanks\n-- \nFrancis\n"},{"id":"46694","messageId":"Pine.LNX.4.64.0707071728330.4093@racer.site","threadId":"8916","inReplyTo":"38b2ab8a0707070851m25d615bdn4f7286cbadaf1316@mail.gmail.com","subject":"Re: git describe origin ?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-07-07T16:33:15Z","receivedAt":"2007-07-07T16:33:15Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 7 Jul 2007, Francis Moreau wrote:\n\n> I was wondering what does 'git describe origin' command mean on a git\n> repo. Does it mean ?\n> \n> a/ git describe origin/HEAD\n> b/ git describe origin/master\n> c/ something else\n\nThis is completely unrelated to \"git describe\". It is about naming \ncommits AKA \"specifying revisions\". You might find the section \"SPECIFYING \nREVISIONS\" in Documentation/git-rev-parse.txt especially helpful. FWIW \nthis section is hinted at in the section \"Symbolic Identifiers\" in \nDocumentation/git.txt.\n\nIf you're too lazy to read, it's a/.\n\n> I also played with git remote and did something silly like: \n> $ git remote add bob /tmp/dummy # dummy does not exist\n> $ git remote show bob\n> fatal: '/tmp/toto': unable to chdir or not a git archive\n> fatal: The remote end hung up unexpectedly\n> ls-remote --heads /tmp/toto: command returned error: 1\n> \n> Maybe the output could be improved to be more readable.\n\nThe first line is very helpful IMHO:\n\n\tfatal: '/tmp/toto': unable to chdir or not a git archive\n\nCiao,\nDscho\n"},{"id":"46696","messageId":"38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@mail.gmail.com","threadId":"8916","inReplyTo":"Pine.LNX.4.64.0707071728330.4093@racer.site","subject":"Re: git describe origin ?","fromName":"Francis Moreau","fromEmail":"francis.moro@gmail.com","sentAt":"2007-07-07T16:53:52Z","receivedAt":"2007-07-07T16:53:52Z","isPatch":false,"sender":{"key":"francis.moro@gmail.com","avatar":null},"body":"Hi,\n\nOn 7/7/07, Johannes Schindelin wrote:\n> On Sat, 7 Jul 2007, Francis Moreau wrote:\n>\n> > I was wondering what does 'git describe origin' command mean on a git\n> > repo. Does it mean ?\n> >\n> > a/ git describe origin/HEAD\n> > b/ git describe origin/master\n> > c/ something else\n>\n> This is completely unrelated to \"git describe\". It is about naming\n> commits AKA \"specifying revisions\". You might find the section \"SPECIFYING\n> REVISIONS\" in Documentation/git-rev-parse.txt especially helpful. FWIW\n> this section is hinted at in the section \"Symbolic Identifiers\" in\n> Documentation/git.txt.\n>\n> If you're too lazy to read, it's a/.\n\nnope I'm not. I'll do read it thanks.\n\n>\n> > I also played with git remote and did something silly like:\n> > $ git remote add bob /tmp/dummy # dummy does not exist\n> > $ git remote show bob\n> > fatal: '/tmp/dummy': unable to chdir or not a git archive\n> > fatal: The remote end hung up unexpectedly\n> > ls-remote --heads /tmp/dummy: command returned error: 1\n> >\n> > Maybe the output could be improved to be more readable.\n>\n> The first line is very helpful IMHO:\n>\n> fatal: '/tmp/dummy': unable to chdir or not a git archive\n>\n\nyep but the 2 others are just noise, aren't they ?\n\nBTW, shouldn't \"git remote add\" have complained at first ?\n\nthanks\n-- \nFrancis\n"},{"id":"46698","messageId":"Pine.LNX.4.64.0707071812570.4093@racer.site","threadId":"8916","inReplyTo":"38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@mail.gmail.com","subject":"Re: git describe origin ?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-07-07T17:14:58Z","receivedAt":"2007-07-07T17:14:58Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 7 Jul 2007, Francis Moreau wrote:\n\n> On 7/7/07, Johannes Schindelin wrote:\n> > On Sat, 7 Jul 2007, Francis Moreau wrote:\n> > \n> > > I also played with git remote and did something silly like:\n> > > $ git remote add bob /tmp/dummy # dummy does not exist\n> > > $ git remote show bob\n> > > fatal: '/tmp/dummy': unable to chdir or not a git archive\n> > > fatal: The remote end hung up unexpectedly\n> > > ls-remote --heads /tmp/dummy: command returned error: 1\n> > >\n> > > Maybe the output could be improved to be more readable.\n> > \n> > The first line is very helpful IMHO:\n> > \n> > fatal: '/tmp/dummy': unable to chdir or not a git archive\n> > \n> \n> yep but the 2 others are just noise, aren't they ?\n\nThere are actually four programs involved, it seems. You get an error \nmessage from all except \"git remote\".\n\n> BTW, shouldn't \"git remote add\" have complained at first ?\n\nNo. Sometimes the URL is not yet available, yet, you want to add it for \nlater reference (think bundles). Sometimes you are simply offline.\n\nCiao,\nDscho\n"},{"id":"46699","messageId":"38b2ab8a0707071027v229b127bq89c56eff5a6cd54f@mail.gmail.com","threadId":"8916","inReplyTo":"Pine.LNX.4.64.0707071812570.4093@racer.site","subject":"Re: git describe origin ?","fromName":"Francis Moreau","fromEmail":"francis.moro@gmail.com","sentAt":"2007-07-07T17:27:42Z","receivedAt":"2007-07-07T17:27:42Z","isPatch":false,"sender":{"key":"francis.moro@gmail.com","avatar":null},"body":"On 7/7/07, Johannes Schindelin wrote:\n> No. Sometimes the URL is not yet available, yet, you want to add it for\n> later reference (think bundles). Sometimes you are simply offline.\n>\n\ntrue.\n\n-- \nFrancis\n"},{"id":"46756","messageId":"38b2ab8a0707080651m2242b518x5313e852621db2cf@mail.gmail.com","threadId":"8916","inReplyTo":"Pine.LNX.4.64.0707071728330.4093@racer.site","subject":"Re: git describe origin ?","fromName":"Francis Moreau","fromEmail":"francis.moro@gmail.com","sentAt":"2007-07-08T13:51:20Z","receivedAt":"2007-07-08T13:51:20Z","isPatch":false,"sender":{"key":"francis.moro@gmail.com","avatar":null},"body":"On 7/7/07, Johannes Schindelin wrote:\n> On Sat, 7 Jul 2007, Francis Moreau wrote:\n>\n> > I was wondering what does 'git describe origin' command mean on a git\n> > repo. Does it mean ?\n> >\n> > a/ git describe origin/HEAD\n> > b/ git describe origin/master\n> > c/ something else\n>\n> This is completely unrelated to \"git describe\". It is about naming\n> commits AKA \"specifying revisions\". You might find the section \"SPECIFYING\n> REVISIONS\" in Documentation/git-rev-parse.txt especially helpful. FWIW\n> this section is hinted at in the section \"Symbolic Identifiers\" in\n> Documentation/git.txt.\n>\n> If you're too lazy to read, it's a/.\n>\n\nOk I took a look to it and I think I get the idea. But now I don't\nunderstand this example taken from \"git-branch\" documentation:\n\n\"\"\"\nDelete unneeded branch\n\n $ git clone git://git.kernel.org/.../git.git my.git\n $ cd my.git\n $ git branch -d -r todo html man (1)\n\"\"\"\n\nI think the last command can't work since the given refs can't be\nfound according the rules given by the documention you mentioned\nearlier.\n\nthanks\n-- \nFrancis\n"}]}