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: Sat, 7 Jul 2007 18:53:52 +0200 [thread overview]
Message-ID: <38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707071728330.4093@racer.site>
Hi,
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/.
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
next prev parent reply other threads:[~2007-07-07 16:53 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 [this message]
2007-07-07 17:14 ` Johannes Schindelin
2007-07-07 17:27 ` Francis Moreau
2007-07-08 13:51 ` Francis Moreau
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=38b2ab8a0707070953s33ca0d1aw879fd3d1a986aaeb@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).