From: "Michael S. Tsirkin" <mst@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: push not resolving commit-ish?
Date: Fri, 24 May 2013 00:26:50 +0300 [thread overview]
Message-ID: <20130523212650.GF31421@redhat.com> (raw)
In-Reply-To: <7v38tde6mr.fsf@alter.siamese.dyndns.org>
On Thu, May 23, 2013 at 02:19:40PM -0700, Junio C Hamano wrote:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
>
> > On Thu, May 23, 2013 at 11:05:00AM -0700, Junio C Hamano wrote:
> >> "Michael S. Tsirkin" <mst@redhat.com> writes:
> >>
> >> > Looks like push can't resolve tags to commits.
> >> > Why is that?
> >>
> >> How else would you push a tag out?
> >
> > Well my reaction is, it seems to figure out it needs a commit and then
> > instead of just getting it, it errors out. Why not just DWIM?
>
> Ahh, that one.
>
> The local branch name hierarchy refs/heads/ is special in that you
> cannot have a tag sitting at the tip, so when "push" decides to
> update something under refs/heads/ on the receiving end, it may not
> be a bad idea to peel it to a commit (and fail if it does not)
> before creating a pack and telling the other end what the value of
> the updated tip should be, and I do not think it will hurt anybody.
Yes, that would help my case.
>
> Restriction in the other direction (i.e. "if push does not go to
> refs/tags/, unconditionally unwrap") is a no-no, though.
prev parent reply other threads:[~2013-05-23 21:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 10:53 push not resolving commit-ish? Michael S. Tsirkin
2013-05-23 10:56 ` Michael S. Tsirkin
2013-05-23 10:56 ` Felipe Contreras
2013-05-23 18:10 ` Junio C Hamano
2013-05-23 21:05 ` Michael S. Tsirkin
2013-05-23 21:06 ` Junio C Hamano
2013-05-23 21:16 ` Michael S. Tsirkin
2013-05-23 21:21 ` Junio C Hamano
2013-05-23 18:05 ` Junio C Hamano
2013-05-23 21:09 ` Michael S. Tsirkin
2013-05-23 21:19 ` Junio C Hamano
2013-05-23 21:26 ` Michael S. Tsirkin [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=20130523212650.GF31421@redhat.com \
--to=mst@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).