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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Feb 18, 2015 at 4:13 PM, Stefan Beller <sbeller@xxxxxxxxxx> 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 notion of an unborn branch is not
> clear to me.
> Maybe
>
>> -               warning(_("remote HEAD refers to nonexistent ref, "
>> -                         "unable to checkout.\n"));
>> +               warning(_("remote HEAD refers to nonexistent ref; "
>> +                         "Checking out $branch instead.\n"));
>
> with $branch being master in the example above. I'd have no idea
> how to come up with a good heuristic which branch to checkout.
> (It would need to match current behavior)

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 into an empty repository.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]