git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Francis Moreau" <francis.moro@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git describe origin ?
Date: Sun, 8 Jul 2007 15:51:20 +0200	[thread overview]
Message-ID: <38b2ab8a0707080651m2242b518x5313e852621db2cf@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707071728330.4093@racer.site>

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

      parent reply	other threads:[~2007-07-08 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-07 15:51 git describe origin ? Francis Moreau
2007-07-07 16:33 ` Johannes Schindelin
2007-07-07 16:53   ` Francis Moreau
2007-07-07 17:14     ` Johannes Schindelin
2007-07-07 17:27       ` Francis Moreau
2007-07-08 13:51   ` Francis Moreau [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38b2ab8a0707080651m2242b518x5313e852621db2cf@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).