Re: [Discuss] soften warning message after cloning "void"

2015-02-20 Thread Junio C Hamano
Stefan Beller writes: > On Wed, Feb 18, 2015 at 6:54 PM, Junio C Hamano wrote: >> On Wed, Feb 18, 2015 at 4:43 PM, Shawn Pearce wrote: >>> >>> This fails from a JGit server because the ref advertisement for an >>> empty repository differs and disagrees with the format used by >>> git-core. The

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Stefan Beller
On Wed, Feb 18, 2015 at 6:54 PM, Junio C Hamano wrote: > On Wed, Feb 18, 2015 at 4:43 PM, Shawn Pearce wrote: >> >> This fails from a JGit server because the ref advertisement for an >> empty repository differs and disagrees with the format used by >> git-core. The result is a confused client spe

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Junio C Hamano
On Wed, Feb 18, 2015 at 4:43 PM, Shawn Pearce wrote: > > This fails from a JGit server because the ref advertisement for an > empty repository differs and disagrees with the format used by > git-core. The result is a confused client spewing an odd checkout > message. That is exactly why the rephr

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Stefan Beller
On Wed, Feb 18, 2015 at 4:25 PM, Junio C Hamano wrote: > On Wed, Feb 18, 2015 at 4:13 PM, Stefan Beller wrote: >>> + warning(_("remote HEAD refers to nonexistent ref; " >>> + "leaving the current branch unborn.\n")); >> >> Personally I find that more confusin

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Shawn Pearce
On Wed, Feb 18, 2015 at 4:43 PM, Shawn Pearce wrote: > On Wed, Feb 18, 2015 at 4:25 PM, Junio C Hamano wrote: >> Checking out a random branch is absolutely the worst thing you can >> do. Personally, I would think that the best thing you can do is to >> educate your users not to clone from a void.

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Shawn Pearce
On Wed, Feb 18, 2015 at 4:25 PM, Junio C Hamano wrote: > Checking out a random branch is absolutely the worst thing you can > do. Personally, I would think that the best thing you can do is to > educate your users not to clone from a void. Create some history > that is worth sharing, and then push

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Junio C Hamano
On Wed, Feb 18, 2015 at 4:13 PM, Stefan Beller wrote: >> + warning(_("remote HEAD refers to nonexistent ref; " >> + "leaving the current branch unborn.\n")); > > Personally I find that more confusing, because I have an idea of > what checkout may refer to. The

Re: [Discuss] soften warning message after cloning "void"

2015-02-18 Thread Stefan Beller
On Wed, Feb 18, 2015 at 3:24 PM, Junio C Hamano wrote: > If you did this: > > $ git init void && > git -C void commit --allow-empty -m initial && > git -C void symbolic-ref HEAD refs/heads/nosuch > $ git clone --no-local void new > > you would get > > warning: remote HEAD r