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
Dustin Sallings <dustin@spy.net>
Date
May 8, 2008, 17:32 UTC
Message-ID
<585390AA-289C-4B2F-B851-DD383C6C7A73@spy.net>
In-Reply-To
<7vprrycce9.fsf@gitster.siamese.dyndns.org>
	Hi, thanks for the response.
On May 7, 2008, at 9:22, Junio C Hamano wrote:
> You got no reactions, neither
> positive nor negative, partly due to this sentence, I suspect.
	I got one response from someone who said he had implemented the same  
thing in one of his branches.  That seemed to confirm the idea for  
me.  Some additional features were suggested to be built on top of  
this, but I didn't read it as necessary for proceeding.
> Please sign-off your patches (see Documentation/SubmittingPatches).
	Oh thanks, I hadn't seen this.  I read it as well as the  
CodingGuidelines document.
Show 11 quoted lines
>> +	When `never`, rebase is never automatically set to true.
>> +	When `local`, rebase is set to true for tracked branches of
>> +	other local branches.
>> +	When `remote`, rebase is set to true for tracked branches of
>> +	remote branches.
>> +	When `always`, rebase will be set to true for all tracking
>> +	branches.
>> +	This option defaults to never.
>
> How does this interact with a similarly named configuration option,
> autosetupmerge, whose settings can be false, true, and always?
	I can direct the user to the autosetupmerge config documentation  
since it also documents the flags that override its behavior.  Is this  
acceptable?
Show 18 quoted lines
>> branch.<name>.remote::
>> 	When in branch <name>, it tells `git fetch` which remote to fetch.
>> 	If this option is not given, `git fetch` defaults to remote  
>> "origin".
>
> This is not your fault, but can anybody guess what the exact command
> sequence to cause the named branch to be advanced by rebasing, only by
> reading this entry?
>
>    branch.<name>.rebase::
>            When true, rebase the branch <name> on top of the fetched  
> branch,
>            instead of merging the default branch from the default  
> remote.
>
> I can't.  Perhaps we would need "when "git pull" is run" or  
> something at
> the end.
	I'll submit this as a separate patch.
> Is this correct?
	[...]
> You might want to check how the setup_tracking() decides when to say
> remote/local in its printf().
	Oh thanks, I clearly didn't understand this and just relied on my  
tests passing by coincidence.
	I'll resubmit my patch with your recommendations, thanks.
-- 
Dustin Sallings
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 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.