From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, git@vger.kernel.org
Subject: Re: push not resolving commit-ish?
Date: Thu, 23 May 2013 11:10:32 -0700 [thread overview]
Message-ID: <7v4ndtftyf.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s18KCYEZaMTn_S2znocyr-WDCT5ciuzLoYaSHPQFc4XCw@mail.gmail.com> (Felipe Contreras's message of "Thu, 23 May 2013 05:56:57 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> On Thu, May 23, 2013 at 5:53 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>> Looks like push can't resolve tags to commits.
>> Why is that?
>>
>> linux$ git push -f $PWD v3.10-rc2:refs/heads/vhost-next
>
> Perhaps v3.10-rc2^{}. Yeah, totally and completely not-user-friendly,
More commonly "v3.10-rc2^0:vhost-next", if you are truly pushing it
out to a remote repository, but then it invites a puzzlement "What
do you plan to do next after pushing? The only reason v3.10-rc2 is
used is because there is not yet a local branch that will host the
vhost-next changes that is built on top of that tag (otherwise you
would be pushing that branch to vhost-next)".
But in this particular case, you are force-pushing into the current
repository, and it is spelled much more commonly
git branch -f vhost-next v3.10-rc2
I would think.
next prev parent reply other threads:[~2013-05-23 18:10 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 [this message]
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
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=7v4ndtftyf.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=mst@redhat.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).