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

Re: [PATCH] Completion: Hint whether amend is the right thing to do.

From
Junio C Hamano <gitster@pobox.com>
Date
May 28, 2008, 23:39 UTC
Message-ID
<7vlk1urob4.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200805290133.48490.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:
Show 7 quoted lines
> onsdagen den 28 maj 2008 17.53.40 skrev Junio C Hamano:
>> Does this mean that it would help reduce mistakes if "git commit --amend"
>> noticed the presense of .dotest-merge but absense of .dotest-merge/amend
>> and refused to operate, I have to wonder?
>
> Well I found myself making these mistakes. That would probably be better. 
> Shouldn't one block commit without amend too then?

If you mean to forbid "git commit" during rebase (perhaps interrupted by s/pick/edit/), I do not think that would fly -- it is the advertised way to split a commit into two, if I am not mistaken.

Previous: Robin RosenbergNext: Shawn O. Pearce
Message 5 of 6 in “Completion: Hint whether amend is the right thing to do.”
  1. Completion: Hint whether amend is the right thing to do.Robin Rosenberg, May 28, 2008
  2. Junio C HamanoMay 28, 2008
  3. Shawn O. PearceMay 28, 2008
  4. Robin RosenbergMay 28, 2008
  5. Junio C HamanoMay 28, 2008
  6. Shawn O. PearceMay 28, 2008

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.