git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: push not resolving commit-ish?

From
Junio C Hamano <gitster@pobox.com>
Date
May 23, 2013, 18:10 UTC
Message-ID
<7v4ndtftyf.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAMP44s18KCYEZaMTn_S2znocyr-WDCT5ciuzLoYaSHPQFc4XCw@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 7 quoted lines
> 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.
Previous: Felipe ContrerasNext: Michael S. Tsirkin
Message 4 of 12 in “push not resolving commit-ish?”
  1. Michael S. TsirkinMay 23, 2013
  2. Michael S. TsirkinMay 23, 2013
  3. Felipe ContrerasMay 23, 2013
  4. Junio C HamanoMay 23, 2013
  5. Michael S. TsirkinMay 23, 2013
  6. Junio C HamanoMay 23, 2013
  7. Michael S. TsirkinMay 23, 2013
  8. Junio C HamanoMay 23, 2013
  9. Junio C HamanoMay 23, 2013
  10. Michael S. TsirkinMay 23, 2013
  11. Junio C HamanoMay 23, 2013
  12. Michael S. TsirkinMay 23, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.