Quoting Björn Steinbrink [off-list ref] writes:
On 2009.10.18 19:34:48 +0900, Nanako Shiraishi wrote:
quoted
Quoting Junio C Hamano [off-list ref]
quoted
When 'frotz' is not a valid object name nor a tracked filename,
we used to complain and failed this command. When there is only
one remote that has 'frotz' as one of its tracking branches, we can
DWIM it as a request to create a local branch 'frotz' forking from
the matching remote tracking branch.
In the subject you used 'git checkout -b frotz origin/frotz'. Did you
forget to say '-t'?
Hm, the DWIMmery only triggers when opts.track is
BRANCH_TRACK_UNSPECIFIED, i.e. -t was not used. And it doesn't change
opts.track when it DWIMs, so it respects branch.autosetupmerge, which
would be overriden by -t. So it seems correct that -t is not in there.
I see.
A user who always wants tracking can set the config option and use
the new "git checkout frotz" shortcut, but a user who usually
doesn't want tracking doesn't have the config option and when he
wants tracking only for this new branch he can explicitly say "git
checkout -t origin/frotz", right?
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/