Re: [RFD] making separate-remote layout easier to use
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Nov 27, 2006, 00:59 UTC
- Message-ID
- <200611270159.14925.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <7vvel2yi2u.fsf@assigned-by-dhcp.cox.net>
On Sunday 26 November 2006 04:58, Junio C Hamano wrote:
Show 9 quoted lines
> > git-clone should skip rewinding branches by default, unless the user > > adds an option (e.g. --include-rewinding-branches). This way new > > users to git.git don't get the `pu` branch unless they really mean > > to get it, at which point they have hopefully also read the upstream's > > description of the `pu` branch and its rewinding policy, and can > > at least start to grasp what is going to happen if they start to > > work with the branch. > > I like this approach very much.
I am not so sure about this. IMHO, any user expects to see "pu" branch cloned too after cloning git.git (at least me, and a newbie probably too).
I agree about the remote branch description saying that "pu" branch will be rewinded. git-clone should set "+" before such a branch.
As said, the real problem begins when the user tries to branch off her own local branch from "pu". At this point, "git branch" or "git checkout -b ..." should warn the user that he has to expect troubles when branching off from such a branch, and only allow it with a "--force" option.