From: Junio C Hamano <gitster@pobox.com>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: John Tapsell <johnflux@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git rebase -i
Date: Thu, 19 Feb 2009 02:09:22 -0800 [thread overview]
Message-ID: <7v63j6oi0d.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <FEE581A3-C858-45CF-B545-8F7187FCCE40@ai.rug.nl> (Pieter de Bie's message of "Thu, 19 Feb 2009 10:00:53 +0000")
Pieter de Bie <pdebie@ai.rug.nl> writes:
> On 19 feb 2009, at 09:21, John Tapsell wrote:
>
>> 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'd prefer something a bit less arbitrary, like using the tracked head
> for a tracking branch.
I'd say that might be a very sane default for users or "branch --track"
and/or "pull --rebase", both for i-rebase and rebase.
next prev parent reply other threads:[~2009-02-19 10:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 9:21 git rebase -i John Tapsell
2009-02-19 9:36 ` Wincent Colaiuta
2009-02-19 9:55 ` John Tapsell
2009-02-19 9:59 ` Wincent Colaiuta
2009-02-19 10:11 ` Jeff King
2009-02-19 10:15 ` Wincent Colaiuta
2009-02-19 10:20 ` Jeff King
2009-02-19 14:57 ` Theodore Tso
2009-02-19 9:50 ` Teemu Likonen
2009-02-19 9:52 ` John Tapsell
2009-02-19 14:02 ` Sitaram Chamarty
2009-02-19 14:24 ` John Tapsell
2009-02-23 0:32 ` Stephan Beyer
2009-02-19 10:00 ` Pieter de Bie
2009-02-19 10:09 ` Junio C Hamano [this message]
2009-02-19 16:12 ` Marc Branchaud
2009-02-19 17:53 ` Nazri Ramliy
2009-02-19 10:01 ` Thomas Rast
2009-02-19 10:03 ` John Tapsell
2009-02-19 10:07 ` Jeff King
2009-02-19 20:55 ` Jay Soffian
2009-02-19 21:04 ` Johannes Schindelin
2009-02-19 21:07 ` Jay Soffian
2009-02-19 23:53 ` Giuseppe Bilotta
2009-02-20 0:07 ` Johannes Schindelin
2009-02-20 0:11 ` Junio C Hamano
2009-02-20 0:26 ` Jay Soffian
2009-02-20 11:02 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v63j6oi0d.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=pdebie@ai.rug.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.