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

Re: Re* Regulator updates for 3.3

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 17, 2012, 06:13 UTC
Message-ID
<7vboq2uaa9.fsf@alter.siamese.dyndns.org>
In-Reply-To
<4F15080C.6060004@pcharlan.com>
Pete Harlan <pgit@pcharlan.com> writes:
> ... The
> only time I think I'd prefer "LEGACY" is if you're planning on
> deprecating and removing it eventually and you want to indicate
> something to that effect in the name.

The discussion that led to the naming of that LEGACY token needs to be re-read, then. The kind of "LEGACY" you prefer is exactly why the environment variable is called LEGACY in the patch you are commenting on, written in response to Linus's suggestion to switch the default, even though I am not 100% buying it.

Having said that, I think I am wasting my time responding to this thread during the feature-freeze period for v1.7.9, as I am not a big fan of switching the default without adequate warning and transition plans, after getting burned by the "'git-foo' vs 'git foo'" flames back in the v1.6.0 release. We would likely to take a gradual and smoother migration route to transition, e.g. v1.7.9 to introduce "merge --edit", v1.7.10 to introduce a configuration variable merge.edit (lack of which gives a warning and an advice message while defaulting to 'no' to preserve the traditional behaviour), and finally v1.8.0 (or v2.0) to flip the default to 'yes' (while the configuration still giving a warning and an advice message) that "merge --no-edit" can still countermand.

So you have until v1.7.10 to decide a good name for the overriding environment variable.

Previous: Pete HarlanNext: Linus Torvalds
Message 14 of 20 in “Re: Regulator updates for 3.3”
  1. Linus TorvaldsJan 10, 2012
  2. Mark BrownJan 10, 2012
  3. Junio C HamanoJan 11, 2012
  4. Linus TorvaldsJan 11, 2012
  5. Junio C HamanoJan 11, 2012
  6. Linus TorvaldsJan 11, 2012
  7. Re* Regulator updates for 3.3Junio C Hamano, Jan 11, 2012
  8. Phil HordJan 11, 2012
  9. Linus TorvaldsJan 11, 2012
  10. Pete HarlanJan 16, 2012
  11. Junio C HamanoJan 16, 2012
  12. Martin FickJan 16, 2012
  13. Pete HarlanJan 17, 2012
  14. Junio C HamanoJan 17, 2012
  15. Linus TorvaldsJan 11, 2012
  16. Paul GortmakerJan 11, 2012
  17. Junio C HamanoJan 13, 2012
  18. Nguyen Thai Ngoc DuyJan 13, 2012
  19. Linus TorvaldsJan 13, 2012
  20. Miles BaderJan 17, 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.