From: Ryan Anderson <ryan@michonline.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Petr Baudis <pasky@suse.cz>, "H. Peter Anvin" <hpa@zytor.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Cogito: cg-clone doesn't like packed tag objects
Date: Tue, 27 Sep 2005 13:34:45 -0400 [thread overview]
Message-ID: <20050927173445.GC23034@mythryan2.michonline.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0509270821590.3308@g5.osdl.org>
On Tue, Sep 27, 2005 at 08:34:22AM -0700, Linus Torvalds wrote:
> On Tue, 27 Sep 2005, Ryan Anderson wrote:
> >
> > git-rev-parse $tagname^0
>
> You need "--verify". Otherwise git-rev-parse will think that you just have
> a strange filename or other random thing:
>
> prompt$ git-rev-parse 000^0
> 000^0
Hmm:
$ cat .git/refs/tags/v2.6.13-rc4
7eab951de91d95875ba34ec4c599f37e1208db93
$ git-rev-parse v2.6.13-rc4
7eab951de91d95875ba34ec4c599f37e1208db93
$ git-rev-parse v2.6.13-rc4^0
63953523341bcafe5928bf6e99bffd7db94b471e
$ git-rev-parse 63953523341bcafe5928bf6e99bffd7db94b471e^0
63953523341bcafe5928bf6e99bffd7db94b471e
# The typo that demonstrates what you did:
$ git-rev-parse 7eab951de91d95875ba34ec4c599f37e1208db93^-
7eab951de91d95875ba34ec4c599f37e1208db93^-
$ git-rev-parse 7eab951de91d95875ba34ec4c599f37e1208db93^0
63953523341bcafe5928bf6e99bffd7db94b471e
So I think --verify is beneficial if you want errors returned, but if
you know you have real tags or commits, git-rev-parse without the
--verify seems to do the right thing.
Or, at the very least, in the case where I used this
(linux/scripts/setlocalversion), this behavior is fine.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-09-27 17:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 22:24 Cogito: cg-clone doesn't like packed tag objects H. Peter Anvin
2005-09-24 1:18 ` Petr Baudis
2005-09-24 1:52 ` H. Peter Anvin
2005-09-24 2:00 ` Junio C Hamano
2005-09-24 12:50 ` Petr Baudis
2005-09-24 17:13 ` Daniel Barkalow
2005-09-24 18:10 ` Junio C Hamano
2005-11-09 22:33 ` Petr Baudis
2005-11-09 23:14 ` Junio C Hamano
2005-11-09 23:36 ` Nick Hengeveld
2005-11-09 23:44 ` Petr Baudis
2005-11-10 1:01 ` Nick Hengeveld
2005-11-09 23:47 ` Junio C Hamano
2005-09-26 21:25 ` Petr Baudis
2005-09-26 21:55 ` Brian Gerst
2005-09-26 21:56 ` Petr Baudis
2005-09-26 22:23 ` Junio C Hamano
2005-09-26 22:29 ` Petr Baudis
2005-09-27 4:46 ` Junio C Hamano
2005-09-27 5:02 ` Tom Prince
2005-09-27 5:28 ` Junio C Hamano
2005-09-27 9:40 ` Petr Baudis
2005-09-27 10:14 ` Josef Weidendorfer
2005-09-27 12:34 ` Petr Baudis
2005-09-27 13:27 ` Josef Weidendorfer
2005-09-27 17:07 ` Junio C Hamano
2005-09-27 17:56 ` Linus Torvalds
2005-09-27 18:36 ` Junio C Hamano
2005-09-27 21:16 ` Linus Torvalds
2005-09-27 21:44 ` Linus Torvalds
2005-09-27 22:11 ` Junio C Hamano
2005-09-28 17:22 ` Junio C Hamano
2005-10-14 6:03 ` Peeling the onion Junio C Hamano
[not found] ` <46a038f90510140048r30c7ec36n35f77a1ac52c4691@mail.gmail.com>
2005-10-14 8:40 ` Junio C Hamano
2005-09-26 22:37 ` Cogito: cg-clone doesn't like packed tag objects Junio C Hamano
2005-09-27 6:54 ` Sven Verdoolaege
2005-09-27 7:25 ` Ryan Anderson
2005-09-27 15:34 ` Linus Torvalds
2005-09-27 17:34 ` Ryan Anderson [this message]
2005-09-27 18:04 ` Linus Torvalds
2005-09-27 7:46 ` Junio C Hamano
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=20050927173445.GC23034@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.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).