From: Jakub Narebski <jnareb@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Junio C Hamano <gitster@pobox.com>,
Alex Riesen <raa.lkml@gmail.com>,
Johannes Sixt <j.sixt@viscovery.net>,
Matthias Andree <matthias.andree@gmx.de>,
Jeff King <peff@peff.net>,
git@vger.kernel.org, Brandon Casey <casey@nrlssc.navy.mil>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: git-tag bug? confusing git fast-export with double tag objects
Date: Sat, 16 May 2009 09:56:24 +0200 [thread overview]
Message-ID: <200905160956.27417.jnareb@gmail.com> (raw)
In-Reply-To: <4A0E67E9.3020208@op5.se>
On Sat, 16 May 2009, Andreas Ericsson wrote:
> Add a tag with a new name, pointing to the original tag. Try doing what
> Matthias did and then run "git show $tagname". It won't show the original
> tag at all, so people have to resort to low-level commands in order to
> see it, but it will still exist as an object.
Not true. Did you check that?
"git show <tag>" shows the whole chain of objects down to non-tag object.
tag tag1
Tagger: Jakub Narebski <jnareb@gmail.com>
Date: Sat May 16 09:55:13 2009 +0200
tag1 (retagged)
tag tag1
Tagger: Jakub Narebski <jnareb@gmail.com>
Date: Sat May 16 09:54:58 2009 +0200
tag1
commit 6d3eee4f5e9fde51f3213320b98bda5f325000e4
[...]
True, the separation between objects could have been made more explicit...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-05-16 8:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 0:53 git-tag bug? confusing git fast-export with double tag objects Matthias Andree
2009-05-14 2:13 ` Matthias Andree
2009-05-14 3:18 ` Junio C Hamano
2009-05-14 9:37 ` Matthias Andree
2009-05-14 12:00 ` Michael J Gruber
2009-05-14 12:16 ` Alex Riesen
2009-05-14 12:51 ` Matthias Andree
2009-05-14 13:16 ` Alex Riesen
2009-05-14 13:39 ` Matthias Andree
2009-05-14 13:42 ` Sverre Rabbelier
2009-05-14 18:02 ` Matthias Andree
2009-05-14 19:01 ` Brandon Casey
2009-05-14 18:22 ` Jeff King
2009-05-14 22:35 ` Matthias Andree
2009-05-15 2:02 ` Jeff King
2009-05-15 12:23 ` Matthias Andree
2009-05-15 13:22 ` Jakub Narebski
2009-05-15 14:54 ` Johannes Sixt
2009-05-15 15:51 ` Alex Riesen
2009-05-15 16:14 ` Matthias Andree
2009-05-15 16:21 ` Andreas Ericsson
2009-05-15 17:40 ` Junio C Hamano
2009-05-16 7:14 ` Andreas Ericsson
2009-05-16 7:56 ` Jakub Narebski [this message]
2009-05-16 8:02 ` Andreas Ericsson
2009-05-16 17:16 ` Junio C Hamano
2009-05-19 11:21 ` Matthias Andree
2009-05-19 11:29 ` Jeff King
2009-05-16 5:07 ` Jeff King
2009-05-15 16:00 ` Daniel Cheng
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=200905160956.27417.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=ae@op5.se \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=matthias.andree@gmx.de \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.com \
--cc=srabbelier@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.