git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Allow local branching to set up rebase by default.

From
Jay Soffian <jaysoffian@gmail.com>
Date
Apr 29, 2008, 21:56 UTC
Message-ID
<76718490804291456r7d1ef385q4e51a5705fdd26ef@mail.gmail.com>
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:
Show 10 quoted lines
> 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.]
Previous: Dustin SallingsNext: Junio C Hamano
Message 2 of 12 in “Allow local branching to set up rebase by default.”
  1. Allow local branching to set up rebase by default.Dustin Sallings, Apr 29, 2008
  2. Jay SoffianApr 29, 2008
  3. Junio C HamanoMay 7, 2008
  4. Dustin SallingsMay 8, 2008
  5. Junio C HamanoMay 8, 2008
  6. Allow tracking branches to set up rebase by default.Dustin Sallings, May 8, 2008
  7. Junio C HamanoMay 10, 2008
  8. Dustin SallingsMay 10, 2008
  9. Allow tracking branches to set up rebase by default.Dustin Sallings, May 10, 2008
  10. Doc: Mention branch.<name>.rebase applies to "git pull"Dustin Sallings, May 8, 2008
  11. Dustin SallingsMay 7, 2008
  12. Junio C HamanoMay 7, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.