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

Possible git bug

From
Hugh Davenport <hugh@davenport.net.nz>
Date
Aug 14, 2013, 04:50 UTC
Message-ID
<9c9e5ea8a9d7e8ef37201cfb8ca9dcc3@davenport.net.nz>
Hey,

Not sure if this is a bug or not. I commonly am finding myself wanting to remove some recent commits, either all or just a select few. So I use rebase in interactive mode for this. The problem I find is that when I do a rebase and leave no commits to pick (where I would think that this would do the same as a reset --hard) just tells me that there is nothing to be done.

So would that be a bug? Or maybe a feature? I would like it that when you do a rebase and select no commits, it will rebase ontop of the commit you chose, and remove all the commits not shown in the interactive listing (so all).

Any ideas are welcome.
Cheers,
Hugh
Next: Daniel Knittl-Frank
Message 1 of 3 in “Possible git bug”
  1. Hugh DavenportAug 14, 2013
  2. Daniel Knittl-FrankAug 14, 2013
  3. Jeff KingAug 14, 2013

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.