Re: git rebase -i
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 20, 2009, 00:07 UTC
- Message-ID
- <alpine.DEB.1.00.0902200105520.10279@pacific.mpi-cbg.de>
- In-Reply-To
- <gnkre1$g8s$1@ger.gmane.org>
Hi,
On Fri, 20 Feb 2009, Giuseppe Bilotta wrote:
Show 26 quoted lines
> On Thursday 19 February 2009 21:55, Jay Soffian wrote: > > > On Thu, Feb 19, 2009 at 4:21 AM, John Tapsell <johnflux@gmail.com> wrote: > >> Hi, > >> > >> I often do 'git rebase -i HEAD~10' to rebase. Since afaics it > >> doesn't matter if you go back 'too far' I just always use HEAD~10 even > >> if it's just for the last or so commit. > >> > >> Would there be any objections to making 'git rebase -i' default to > >> HEAD~10 or maybe 16 or 20. Having sensible defaults for commands > >> helps a bit with making it easier to use. > > > > I think the following might be reasonable to support: > > > > $ git rebase -i -10 > > $ git rebase -i -n -10 > > This feature gets my vote. I actually gave the implementation a quick try, > but didn't get very far through it. I was actually considering making git > rev-parse support the syntax. > > Yes, as remarked by Johannes there are issue when there are merges in between > (in which case -10 is most likely not the same as HEAD~10), but I would say > that this is in no way a good reason to deprive users from the comfort it can > give in most common situations.
"I want it, I want it, I want it, and I'll just ignore what you just said" is not a good counterargument, would you say?
Sure, you even cited me, responding to the mail I responded to (as opposed to my mail), but you managed to ignore my argument nevertheless.
Ciao, Dscho