From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Tags of non-commits
Date: Fri, 24 Aug 2007 11:49:23 -0700 [thread overview]
Message-ID: <7vwsvkdaz0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708241337560.5774@iabervon.org> (Daniel Barkalow's message of "Fri, 24 Aug 2007 14:11:33 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> There seems to be an inconsistency between the fetch and tag over whether
> lightweight tags of non-commits are allowed. Fetch doesn't like them, but
> tag creates them without any particular fuss.
Is your "fetch does not like them" about the automated
following? If you say "git fetch $remote tag $that_tag" there
shouldn't be any difference.
And the difference in the automated following behaviour is
deliberate. Lightweight ones tend to be private "anchor point"
during development (these days we need that less often, thanks
to reflogs), and annotated ones, especially the signed kinds are
meant for public consumption.
next prev parent reply other threads:[~2007-08-24 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 18:11 Tags of non-commits Daniel Barkalow
2007-08-24 18:49 ` Junio C Hamano [this message]
2007-08-24 19:13 ` Daniel Barkalow
2007-08-24 20:26 ` 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=7vwsvkdaz0.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--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).