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

Re: [PATCH v5 0/3] pull: stop warning on every pull

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 11, 2020, 07:17 UTC
Message-ID
<xmqqo8j0io39.fsf@gitster.c.googlers.com>
In-Reply-To
<20201210100538.696787-1-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> The discussion about making fast-forward-only pulls the default is
> stuck on mud, and there's no agreement about what we should even
> be warning our users about.

The above perception of yours is mostly due to misunderstanding, I would have to say. We are in agreement on what we should be warning about at least, assuming that you are expressing what you want clearly in the latest round of responses and I understood them correctly [*1*].

I do not know if others on the list agree, though.

I do agree that there is no agreement on the behaviour in the endgame. In principle, I am in favor of disabling the more dangerous half of the "git pull" command for those who haven't configured anything. But I can understand those who do not want that behaviour, as the fallout would be quite big.

> Even my straightforward patches about improving documentation, and
> the consistency of the UI with --merge and other obvious fixes
> lost traction.

It may be obvious to you, but may not be to others on the list who spoke in the thread and who didn't speak but read the discussion.

I did see potential goodness in the documentation update and that was why I offered polishment on top of your patches in a v3 round, but seeing the suggestions dismissed without convincing arguments before v4 was sent out would have discouraged even the most patient reviewers among us. If you meant by "lost traction" the lack of comments on v4, that was my reason for not commenting.

In any case, these three patches in this round looked quite sensible to me, except for the tests in 3/3, and minor details of 2/3, both of which I gave a more detailed review and suggestion.

Thanks.
[Footnote]

*1* The only difference between us is whether it is sensible to allow explicitly ask to see the same behaviour as an unconfigured user except for the help text---I do not think it is, and I do want to avoid introducing pull.mode, but I've shown a way or two to get the behaviour without adding pull.mode in the mix.

Previous: Felipe ContrerasNext: Felipe Contreras
Message 22 of 26 in “pull: stop warning on every pull”
  1. 0/3 pull: stop warning on every pullFelipe Contreras, Dec 10, 2020
  2. 2/3 pull: move default warningFelipe Contreras, Dec 10, 2020
  3. Junio C HamanoDec 11, 2020
  4. Felipe ContrerasDec 11, 2020
  5. Junio C HamanoDec 12, 2020
  6. Felipe ContrerasDec 12, 2020
  7. Junio C HamanoDec 13, 2020
  8. Felipe ContrerasDec 14, 2020
  9. Felipe ContrerasDec 12, 2020
  10. 1/3 pull: refactor fast-forward checkFelipe Contreras, Dec 10, 2020
  11. Junio C HamanoDec 11, 2020
  12. Felipe ContrerasDec 12, 2020
  13. 3/3 pull: display default warning only when non-ffFelipe Contreras, Dec 10, 2020
  14. Junio C HamanoDec 11, 2020
  15. Felipe ContrerasDec 11, 2020
  16. Junio C HamanoDec 11, 2020
  17. Felipe ContrerasDec 12, 2020
  18. Junio C HamanoDec 12, 2020
  19. Felipe ContrerasDec 12, 2020
  20. Junio C HamanoDec 14, 2020
  21. Felipe ContrerasDec 14, 2020
  22. Junio C HamanoDec 11, 2020
  23. Felipe ContrerasDec 11, 2020
  24. Junio C HamanoDec 12, 2020
  25. Felipe ContrerasDec 12, 2020
  26. Felipe ContrerasDec 14, 2020

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.