From: "Michael S. Tsirkin" <mst@redhat.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>, git@vger.kernel.org
Subject: Re: push not resolving commit-ish?
Date: Fri, 24 May 2013 00:16:47 +0300 [thread overview]
Message-ID: <20130523211647.GC31421@redhat.com> (raw)
In-Reply-To: <7v4ndtftyf.fsf@alter.siamese.dyndns.org>
On Thu, May 23, 2013 at 11:10:32AM -0700, Junio C Hamano wrote:
> 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)".
This was just a bad example.
The real reason is this:
I have a development branch, vhost-next. I have a tag there
like for_linus for things that are ready to go out.
I don't always point it at the tip of the branch
since I might want to rebase/amend X last commits.
It's a tag and not a branch since I need to sign the tag.
I push to a branch and not just the tag since this way
people can track it and do downstream development on top.
So pushing the tag to branch would save me some churn.
> 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 21:16 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 [this message]
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=20130523211647.GC31421@redhat.com \
--to=mst@redhat.com \
--cc=felipe.contreras@gmail.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).