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

Re: feature request

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 27, 2016, 22:46 UTC
Message-ID
<xmqqwpgt4dgj.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CALj-rGfAyimf0nFFcDHVHUgj8PQaz6Cvoz_PQfqdhr=QJEpbRw@mail.gmail.com>
John Rood <mr.john.rood@gmail.com> writes:
Show 18 quoted lines
> On Thu, Oct 27, 2016 at 5:30 PM, Stefan Beller <sbeller@google.com> wrote:
>> On Thu, Oct 27, 2016 at 2:55 PM, John Rood <mr.john.rood@gmail.com> wrote:
>>> 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.
>>
>> Look at the -m option of git commit,
>>
[administrivia: do not top post]
Show 7 quoted lines
> Thanks, I think changing the default for windows is a good idea.
>
> The -m indeed accomplishes one-line messages when you are voluntarily
> doing a commit. However, the scenario I mentioned is "When users pull
> commits, and a new commit needs to be created for the merge"  In this
> situation, the user isn't issuing the "git commit" command, and so
> he/she doesn't have the opportunity to use the -m flag.
There is --no-edit there.
Previous: John RoodNext: David Lang
Message 11 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.