git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Dustin Sallings" <dustin@spy.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow local branching to set up rebase by default.
Date: Tue, 29 Apr 2008 17:56:45 -0400	[thread overview]
Message-ID: <76718490804291456r7d1ef385q4e51a5705fdd26ef@mail.gmail.com> (raw)
In-Reply-To: <1209502182-39800-1-git-send-email-dustin@spy.net>

On Tue, Apr 29, 2008 at 4:49 PM, Dustin Sallings <dustin@spy.net> wrote:
> Change cd67e4d4 introduced a new configuration parameter that told
>  pull to automatically perform a rebase instead of a merge.  I use this
>  feature quite a bit in topic branches and would like it to be the
>  default behavior for a topic branch.
>
>  If the parameter branch.autosetuprebase applies for a branch that's
>  being created, that branch will have branch.<name>.rebase set to true.
>
>  See the documentation for how this may be applied.
>

I've had this change parked in one of my branches forever. Consider
this a UI suggestion to go with the new config option?

    [WIP] new --rebase option to set branch.*.rebase for new branches

    Add a --rebase option to git-branch and git-checkout. If given, it
    implies --track but additionally sets branch.<newbranch>.rebase to true.

    [NOTE TO SELF: this is based off the old next branch, and also it sitting on
    top of my old --track changes, so it will need to be reworked.]

  reply	other threads:[~2008-04-29 21:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 20:49 [PATCH] Allow local branching to set up rebase by default Dustin Sallings
2008-04-29 21:56 ` Jay Soffian [this message]
     [not found]   ` <02471C27-C99D-43E7-BC58-50F2B86ED159@spy.net>
2008-05-07  6:01     ` Dustin Sallings
2008-05-07 15:19       ` Junio C Hamano
2008-05-07 16:22 ` Junio C Hamano
2008-05-08 17:32   ` Dustin Sallings
2008-05-08 18:23     ` Junio C Hamano
2008-05-08 18:28   ` [PATCH] Allow tracking branches " Dustin Sallings
2008-05-10 18:41     ` Junio C Hamano
2008-05-10 22:36       ` Dustin Sallings
2008-05-10 22:36       ` Dustin Sallings
2008-05-08 18:28   ` [PATCH] Doc: Mention branch.<name>.rebase applies to "git pull" Dustin Sallings

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=76718490804291456r7d1ef385q4e51a5705fdd26ef@mail.gmail.com \
    --to=jaysoffian@gmail.com \
    --cc=dustin@spy.net \
    --cc=git@vger.kernel.org \
    /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).