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

Re: [PATCH v3] push: Enhance unspecified push default warning

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 6, 2013, 19:01 UTC
Message-ID
<xmqqk3gl8id0.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1839883487.4893076.1383646619137.JavaMail.root@imag.fr>
Matthieu Moy <matthieu.moy@grenoble-inp.fr> writes:
> I don't remember all the discussions on the patch which introduced
> the warning, but I don't think it's relevant to digg them before applying the patch:
If we apply the patch then it is too late to dig them ;-)
Show 5 quoted lines
> * The assumption was that users would read the docs, but as I already mentioned:
>   "Judging by the question asked on stackoverflow
>   ( http://stackoverflow.com/questions/13148066/warning-push-default-is-unset-its-implicit-value-is-changing-in-git-2-0 )
>   and its popularity, telling the users to read the docs did not work very
>   well."

That is true, but does it justify giving a misleading information in the advice message?

Specifically:
>> +   "When push.default is set to 'matching', git will push all local branches\n"
>> +   "to the remote branches with the same (matching) name.

invites those who do not read documentation to mistake it with using an explicit "refs/heads/*:refs/heads/*" refspec.

And this one
>> +   "In Git 2.0 the new push.default of 'simple' will push only the current\n"
>> +   "branch to the same remote branch used by git pull.   A push will\n"
>> +   "only succeed if the remote and local branches have the same name.\n"

while you can see that it is not telling a lie if you read it twice, "will only succeed if" feels somewhat roundabout.

	... push only the current branch back to the branch of the
	same name, but only if 'git pull' is set to pull from that
	branch. Otherwise the push will fail.
might be an improvement, but I dunno.
> * The warning has been there for a while now. Advanced users have
> already set push.default.  We shouldn't be worried about eating a
> bit of screen real estate for users who didn't yet.
This part I can agree with.
Previous: Matthieu MoyNext: Junio C Hamano
Message 6 of 20 in “push: Enhance unspecified push default warning”
  1. push: Enhance unspecified push default warningGreg Jacobson, Oct 4, 2013
  2. Greg JacobsonNov 3, 2013
  3. Junio C HamanoNov 4, 2013
  4. Matthieu MoyNov 5, 2013
  5. Matthieu MoyNov 5, 2013
  6. Junio C HamanoNov 6, 2013
  7. Junio C HamanoNov 6, 2013
  8. Junio C HamanoNov 6, 2013
  9. Matthieu MoyNov 6, 2013
  10. Jonathan NiederNov 6, 2013
  11. Matthieu MoyNov 7, 2013
  12. Junio C HamanoNov 7, 2013
  13. Matthieu MoyNov 7, 2013
  14. Junio C HamanoNov 8, 2013
  15. Junio C HamanoNov 8, 2013
  16. Marc BranchaudNov 8, 2013
  17. Junio C HamanoNov 11, 2013
  18. Jonathan NiederNov 11, 2013
  19. Marc BranchaudNov 11, 2013
  20. Matthieu MoyNov 11, 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.