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

Re: [PATCH/RFC] Allow empty commits during rebase -i

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 18, 2010, 10:01 UTC
Message-ID
<alpine.DEB.1.00.1001181059510.4985@pacific.mpi-cbg.de>
In-Reply-To
<4B53C355.1010109@pcharlan.com>
Hi,
On Sun, 17 Jan 2010, Pete Harlan wrote:
> If the introduction of empty commits that the user has asked for 
> (perhaps inadvertently) is considered too undesirable, then perhaps my 
> fix is too simple.  I'll think about how to do something more 
> sophisticated.

How about something less sophisticated instead? Namely, check for the condition that nothing was changed, and tell the user that the commit blablabla seems to introduce changes that are already present in HEAD. Maybe even mention that this may be due to the commit being applied already and saying that --continue is safe in that case, but please check.

Hmm?

Ciao, Dscho

Previous: Junio C Hamano
Message 5 of 5 in “Allow empty commits during rebase -i”
  1. Allow empty commits during rebase -iPete Harlan, Jan 18, 2010
  2. Junio C HamanoJan 18, 2010
  3. Pete HarlanJan 18, 2010
  4. Junio C HamanoJan 18, 2010
  5. Johannes SchindelinJan 18, 2010

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.