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

Re: Regulator updates for 3.3

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 11, 2012, 02:28 UTC
Message-ID
<7vmx9v7z1r.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CA+55aFxvQF=Bm4ae6euB_UO8otMCuN9Lv37Zn3TpE-L7JH3Kzw@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
> Addid junio and git to the cc just to bring up this issue of bad UI
> once again. I realize it could break old scripts to start up an editor
> window, but still..

It is a non-starter to unconditionally start an editor. We would need a good way for users to conveniently say "I am doing this unusual merge that needs to be justified, and I want an editor to write my justification".

Obviously, "git merge -e regulator/for-linus" would work and is just three keystrokes, which can be said "convenient enough" once the user gets used to, but I think this is still inadequate as a solution, as the real problem is it is _too_ easy to forget to give the option. Until the user becomes _aware_ of the issues, it will not even occur to the user that s/he _has_ to justify a merge (or not create a merge at all) in certain circumstances and directions. After all, you have been repeating the "do not make meaningless merges" for the past five years on the list. UI tweak alone will not fix that.

If we are to rely on user's conscious action, I think it may be something like a set of configurations that say things like:

 - This branch is for advancing a specific topic, and not for merging
   random development that happen elsewhere;
 - This branch is for merging works by people downstream from me;
 - This remote tracking branch (and by extension that branch at that
   remote that uses this as its remote tracking branch) is my upstream and
   I should not be merging back from it; and
 - This remote tracking branch is my downstream, and I should freely merge
   it when I heard it is ready.

and depending on the combination of what is being merged into what, toggle the --edit option by default for "git merge" when neither "--edit" nor "--no-edit" is given, just like "git merge" defaults to "--edit" when merging an annotated tag.

Previous: Mark BrownNext: Linus Torvalds
Message 3 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.