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

feature request

From
John Rood <mr.john.rood@gmail.com>
Date
Oct 27, 2016, 21:55 UTC
Message-ID
<CALj-rGeoT_mpmuw8Put=6eRhzf-r2WUohu_Kd-wnpc=BvO5joA@mail.gmail.com>
Users should be able to configure Git to not send them into a Vim editor.

When users pull commits, and a new commit needs to be created for a merge, Git's current way of determining a commit message is to send the user into a Vim window so that they can write a message. There are 2 reasons why this might not be the ideal way to prompt for a commit message.

1. Many users are used to writing concise one-line commit messages and
would not expect to save a commit message in a multi-line file. Some
users will wonder why they are in a text editor or which file they are
editing. Others may not, in fact, realize at all that a text editor is
what they are in.
2. Many users are not familiar with Vim, and do not understand how to
modify, save, and exit. It is not very considerate to require a user
to learn Vim in order to finish a commit that they are in the middle
of.
The existing behavior should be optional, and there should be two new options:
1. Use a simple inline prompt for a commit message (in the same way
Git might prompt for a username).
2. Automatically assign names for commits in the form of "Merged x into y".
Next: Stefan Beller
Message 1 of 14 in “feature request”
  1. John RoodOct 27, 2016
  2. Stefan BellerOct 27, 2016
  3. John RoodOct 27, 2016
  4. John RoodOct 27, 2016
  5. Junio C HamanoOct 27, 2016
  6. John RoodOct 27, 2016
  7. Junio C HamanoOct 27, 2016
  8. John RoodOct 27, 2016
  9. Stefan BellerOct 27, 2016
  10. John RoodOct 27, 2016
  11. Junio C HamanoOct 27, 2016
  12. David LangOct 27, 2016
  13. Johannes SchindelinOct 28, 2016
  14. Philip OakleyOct 28, 2016

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.