From: Andreas Schwab <schwab@linux-m68k.org>
To: Rolf Leggewie <foss@rolf.leggewie.biz>
Cc: git@vger.kernel.org
Subject: Re: prevent push of irrelevant tags
Date: Thu, 12 Apr 2012 22:34:12 +0200 [thread overview]
Message-ID: <m2bomwy9iz.fsf@igel.home> (raw)
In-Reply-To: <4F873153.9060004@rolf.leggewie.biz> (Rolf Leggewie's message of "Fri, 13 Apr 2012 03:47:31 +0800")
Rolf Leggewie <foss@rolf.leggewie.biz> writes:
> I just ran into the situation that "git push --tags" pushed tags to the
> remote repo that point to commits that do not exist there. How can this
> happen?
A tag is just a ref like any other.
> Git has the information to know that tag X will be useless in repo Y
> because the commit Z it points to does not exist in Y.
It is not useless. After you pushed the tag the commit Z it points to
exists now in Y as well.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2012-04-12 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 19:47 prevent push of irrelevant tags Rolf Leggewie
2012-04-12 20:07 ` Junio C Hamano
2012-04-12 20:45 ` Rolf Leggewie
2012-04-12 20:34 ` Andreas Schwab [this message]
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=m2bomwy9iz.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=foss@rolf.leggewie.biz \
--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).