Re: confusion over the new branch and merge config
- From
Jakub Narebski <jnareb@gmail.com>
- Date
- Dec 23, 2006, 08:31 UTC
- Message-ID
- <emipbt$f4m$3@sea.gmane.org>
- In-Reply-To
- <20061223051210.GA29814@segfault.peff.net>
Jeff King wrote:
Show 5 quoted lines
> It also means that even without a remote, the merge option makes sense > (e.g., if I do repeated merges from one local branch to another). And it > means that it's _always_ correct for "checkout -b <new> <track>" to set > branch.<new>.merge to <track>, without having to worry about finding an > appropriate remote.
Without remote (or rather with remote ".") remote branch names are the same as tracking branch names :-)
-- Jakub Narebski Warsaw, Poland ShadeHawk on #git