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

Re: "git push" silently fails, says 'Everything up-to-date" when it's not.

From
Junio C Hamano <gitster@pobox.com>
Date
May 29, 2012, 18:53 UTC
Message-ID
<7vipfe4y50.fsf@alter.siamese.dyndns.org>
In-Reply-To
<vpqipfgec9k.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
> I don't know what can be done to improve the case of detached HEAD with
> push.default=matching. Perhaps Git should warn when HEAD is not pushed
> (detached HEAD, or HEAD points to a branch that doesn't exist remotely)?

Please don't. For those whose workflow clearly separates local history building (checking different branches, making commits, etc.) and publishing the result (git push), "git push" is *not* a way to say "I am done with the work I have been doing on *this* branch", but is a way to say "I am done for the day, and all the branches I push out are in good order". It does not matter what branch the user happens to be on when "git push" is run for them (including me).

Previous: Matthieu Moy
Message 3 of 3 in “"git push" silently fails, says 'Everything up-to-date" when it's not.”
  1. David WoodhouseMay 28, 2012
  2. Matthieu MoyMay 28, 2012
  3. Junio C HamanoMay 29, 2012

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.