Re: git rebase -i

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 20, 2009, 00:11 UTC
Message-ID: <7vzlgij7cb.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <76718490902191255w24b30bd8jacaed8aa919d6526@mail.gmail.com>

Jay Soffian <jaysoffian@gmail.com> writes:

Show 15 quoted lines

> 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

The syntax would certainly imply a different semantics from giving HEAD~10. How would you compute the set of commits to rebase sanely when you have merges after your 10th direct parent commit?