On Tue, Apr 29, 2008 at 4:49 PM, Dustin Sallings <dustin@xxxxxxx> 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.]
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
