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

Re: git rebase stops on empty commits

From
MBMark Blakeney <markb@berlios.de>
Date
Jul 22, 2009, 23:01 UTC
Message-ID
<loom.20090722T224408-68@post.gmane.org>
In-Reply-To
<20090723070812.6117@nanako3.lavabit.com>

Because these particular original commits were real commits ported from our previous archaic system which for technical reasons have lost the actual file changes (although they are trivial for each of these particular cases). But all our commit comments are very verbose and valuable, specifically in these cases, so it would be a shame to lose them from the linear change history.

Anyway, the question of why anybody would want empty commits is beside the main point. The fact is that git provides this option so my bug sugestion here is that git rebase does not cater for this existing git commit option very well. My contention is that "git commit" supports --allow-empty so "git rebase" should as well.

Previous: Nanako Shiraishi
Message 6 of 6 in “git rebase stops on empty commits”
  1. Mark BlakeneyJul 22, 2009
  2. Mark BlakeneyJul 22, 2009
  3. Peter KreftingJul 22, 2009
  4. Mark BlakeneyJul 22, 2009
  5. Nanako ShiraishiJul 22, 2009
  6. Mark BlakeneyJul 22, 2009

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.