Re: Difficulties in advertising a new branch to git newbies
- From
Junio C Hamano <junkio@cox.net>
- Date
- Feb 6, 2007, 19:14 UTC
- Message-ID
- <7vwt2vgkuc.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <87wt2vce31.wl%cworth@cworth.org>
Carl Worth <cworth@cworth.org> writes:
Show 16 quoted lines
> On Mon, 05 Feb 2007 22:37:42 -0800, Junio C Hamano wrote: >> Carl Worth <cworth@cworth.org> writes: >> >> > So, could we fix this so that a remote branch name will resolve >> > without the "origin/" prefix if it is not ambiguous? >> >> I am fairly negative on this one, especially I do not think the >> symptom deserves to be described with the word "fix". DWIM is >> good, but it has bounds, and this particular one feels it is >> slightly on the other side of the boundary. > > I can accept that argument. > > With "fix" I was referring to the backwards-compatibility problem, > (that I don't have a way to give branch checkout instructions to users > that will work for both 1.5 and pre-1.5 versions of git).
If you tell your users to --use-separate-remote in the "git clone" instruction, would that solve your backward compatibility problem?