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

Re: [PATCH v3] Add core.mode configuration

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 16, 2013, 23:06 UTC
Message-ID
<20131016230634.GO9464@google.com>
In-Reply-To
<8629441933A94862982C5CDD6BF47690@PhilipOakley>
Philip Oakley wrote:
Show 5 quoted lines
> Would this be a good time to suggest a specific wording should be
> proposed (or a reminder of what was proposed repeated) for the
> documentation of this option. It will be the documentation that
> users will refer to when they need to know, rather than the list
> discussions.
It's not clear to me that this config item is a good idea.

What is the intended use? If someone wants to test that their scripts will continue to work with git 2.0, wouldn't testing a 2.0 release candidate (or the current state of the 'jch' branch until one exists) be the simplest way to do that? If someone just likes the proposed behavior changes and wants to start using them right away, maybe we can help them by releasing 2.0 sooner ;-), or by advertising the fairly simple changes in commandline usage to get the new behaviors:

	Instead of "git add", use "git add -A".
	When using "git add -u" or "git add -A" from a subdirectory
	of the toplevel, specify "git add -u ." explicitly unless you
	want it to apply to the whole tree (in which case use
	"git add -u :/").
	Instead of letting "git push" guess, name the branch you
	want to push: "git push origin master".  Or set
	'[push] default = simple' in your configuration.
	Pass --prefix to "git svn clone".

The downside of configuration like the proposed core.next is that it is hard to explain ("What do you mean that I can't roll back to the pre-2.0 behavior in Git 2.0 by setting this configuration setting to an appropriate value?"), users or scripts can rely on it, and configuration variables tend to accumulate and never be removed. If we really want a run-time switch for this, I suspect an appropriately named environment variable would work better, since we have a history of being able to remove those without alarming people.

My two cents, Jonathan

Previous: Philip OakleyNext: Philip Oakley
Message 18 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.