Re: git describe origin ?
- From
- Francis Moreau <francis.moro@gmail.com>
- Date
- Jul 8, 2007, 13:51 UTC
- Message-ID
- <38b2ab8a0707080651m2242b518x5313e852621db2cf@mail.gmail.com>
- In-Reply-To
- <Pine.LNX.4.64.0707071728330.4093@racer.site>
On 7/7/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
Show 17 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/. >
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