Re: [PATCH/RFC] Convenient support of remote branches in git-checkout
- From
Junio C Hamano <junkio@cox.net>
- Date
- Nov 7, 2006, 02:08 UTC
- Message-ID
- <7v7iy89ffs.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <7vd5809fnh.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 12 quoted lines
> Josef Weidendorfer <Josef.Weidendorfer@gmx.de> writes: > >> What do you think about the setup of the default for "git-pull"? > > I personally feel that is loading "checkout" with too many > different things. > > It might be easier to maintain in the long term to have a helper > command 'git-fork' to handle the gory details of forking off > from an existing branch (merge default setting, branch creation, > what else will we have next month? ;-) and perhaps automatically > call it from git-checkout as a short-hand.
Ah, one should never open one's mouth before thinking things twice and then sleeping on it.
I do not think we want a _new_ command. It may make sense to enrich 'git-branch' for that.
If "git-checkout -b" does not use 'git-branch' to create a new branch in the current code, maybe we should, regardless of the usability enhancements under discussion.