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