From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux fatal: cannot describe <sha1>
Date: Tue, 1 Jul 2008 22:09:51 +0200 [thread overview]
Message-ID: <20080701200951.GB10677@uranus.ravnborg.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0807011817230.20393@fbirervta.pbzchgretzou.qr>
On Tue, Jul 01, 2008 at 06:20:17PM +0200, Jan Engelhardt wrote:
> Hi,
>
>
> Just a note that when you run git-describe, you should probably quiten it.
>
> fatal: cannot describe 'bd7364a0fd5a4a2878fe4a224be1b142a4e6698e'
>
> This happens when tags are not present, which can happen if Linus's tree
> is sent upwards again, IOW:
>
> machine1$ git-clone torvalds/linux-2.6.git
> machine1$ git push elsewhere master
>
> machine2$ git-clone elsewhere:/linux
> machine2$ git-describe HEAD
> fatal: cannot describe that
Hi Jan.
Any specific reason why you sent it to me?
Maybe because I do not use git describe at all?
Sam
next prev parent reply other threads:[~2008-07-01 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 16:20 Jan Engelhardt
2008-07-01 20:09 ` Sam Ravnborg [this message]
2008-07-01 22:18 ` Sebastian Siewior
2008-07-05 12:58 ` Jan Engelhardt
2008-07-06 21:13 ` Sam Ravnborg
2008-07-06 21:34 ` Sam Ravnborg
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=20080701200951.GB10677@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jengelh@medozas.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®