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

Re: [PATCH v3] Add core.mode configuration

From
KMKrzysztof Mazur <krzysiek@podlesie.net>
Date
Oct 15, 2013, 22:01 UTC
Message-ID
<20131015220125.GA14021@shrek.podlesie.net>
In-Reply-To
<525d8ebd19c67_5feab61e8037@nysa.notmuch>
On Tue, Oct 15, 2013 at 01:51:41PM -0500, Felipe Contreras wrote:
> 
> I don't see what is the problem. We haven't had the need for push.default =
> simplewarning, have we? If you want the warning, you don't change anything, if

simplewarning makes no sense, because push.default=simple sets exact behavior, not some "next" behavior that may change in future.

For instance, I was very unhappy once, when git pull failed and said that I should do git pull --merge.

Show 7 quoted lines
> you want to specify something, you already know what you are doing.
> 
> > Maybe we should also add core.mode=next-warn that changes defaults like next
> > but keeps warnings enabled until the user accepts that change by setting
> > appropriate config option?
> 
> Maybe, but would you actually use that option?
No.
Show 15 quoted lines
> 
> > That's safer than next (at least for interactive use) and maybe more users
> > would use that, but I don't think that's worth adding.
> 
> Maybe, but I don't think many users would use either mode, and that's good.
> 
> > For me, old behavior by default and warnings with information how to
> > enable new incompatible features, is sufficient. So I don't need
> > core.mode option, but as long it will be useful for other users I have
> > nothing against it.
> 
> OK, but that seems to mean you don't need core.mode = next-warn either. I'm not
> against adding such a mode, but I would like to hear about _somebody_ that
> would like to actually use it. I don't like to program for ghosts.
>

As I said earlier, I don't think that next-warn it's worth adding, but such option might increase the number of people interested in the core.mode.

Krzysiek
Previous: Felipe ContrerasNext: Felipe Contreras
Message 22 of 25 in “Add core.mode configuration”
  1. Add core.mode configurationFelipe Contreras, Oct 12, 2013
  2. Krzysztof MazurOct 14, 2013
  3. Felipe ContrerasOct 14, 2013
  4. Krzysztof MazurOct 15, 2013
  5. Felipe ContrerasOct 15, 2013
  6. Krzysztof MazurOct 15, 2013
  7. Felipe ContrerasOct 15, 2013
  8. Krzysztof MazurOct 15, 2013
  9. John SzakmeisterOct 15, 2013
  10. Felipe ContrerasOct 16, 2013
  11. Krzysztof MazurOct 16, 2013
  12. Felipe ContrerasOct 16, 2013
  13. John SzakmeisterOct 16, 2013
  14. John SzakmeisterOct 16, 2013
  15. Felipe ContrerasOct 16, 2013
  16. Felipe ContrerasOct 16, 2013
  17. Philip OakleyOct 16, 2013
  18. Jonathan NiederOct 16, 2013
  19. Philip OakleyOct 17, 2013
  20. Felipe ContrerasOct 17, 2013
  21. Felipe ContrerasOct 15, 2013
  22. Krzysztof MazurOct 15, 2013
  23. Felipe ContrerasOct 16, 2013
  24. Krzysztof MazurOct 16, 2013
  25. Felipe ContrerasOct 16, 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.