git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Pieter de Bie <pdebie@ai.rug.nl>,
	Git Mailinglist <git@vger.kernel.org>
Subject: Re: [PATCH] Add option to git-branch to set up automatic rebasing
Date: Thu, 19 Jun 2008 12:14:23 -0700	[thread overview]
Message-ID: <7vr6attey8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080619154350.GA21625@atjola.homenet

Björn Steinbrink <B.Steinbrink@gmx.de> writes:

> On 2008.06.19 15:00:19 +0100, Johannes Schindelin wrote:
>> Hi,
>> 
>> On Thu, 19 Jun 2008, Pieter de Bie wrote:
>> 
>> > This functionality was actually introduced in
>> >  0a02186f924aee1bd69f18ed01f645aa332ce0d1, but can only be activated by the
>> > configuration flag. Now we can also setup auto rebasing using the --rebase
>> > flag in git-branch or git-checkout, similar to how --track works.
>> 
>> How about "--rebasing"?  I would scratch my head a bit how a new branch 
>> and a rebase would go together.
>
> Hm, --rebasing sounds weird to me as well. Maybe --track=merge and
> --track=rebase, with --track being equal to --track=merge?

That looks like the best wording so far, although I suspect that the true
reason why all of the above sounds confusing may be because the concept
itself is not clear.

  reply	other threads:[~2008-06-19 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19  0:53 [PATCH] Add option to git-branch to set up automatic rebasing Pieter de Bie
2008-06-19 14:00 ` Johannes Schindelin
2008-06-19 14:10   ` Pieter de Bie
2008-06-19 15:43   ` Björn Steinbrink
2008-06-19 19:14     ` Junio C Hamano [this message]
2008-06-19 22:58       ` Pieter de Bie
2008-06-19 23:24         ` Junio C Hamano

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=7vr6attey8.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=B.Steinbrink@gmx.de \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).