Re: git pull with "no common commits" : danger?

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

 



Junio C Hamano <gitster@xxxxxxxxx> writes:

>
> ...
>
> But I would be unhappy if I have to be the one to hear complaints from
> newbies who are now forced to add an obscure option to his "git pull" in
> the second case.
>
> So this is not so cut-and-dried from the usability point of view as you
> seem to think.

I understand your reasoning for the second case, and the init/pull sequence
is something I used to do too. Thanks for the explanations.

Regarding this init/pull sequence: it might be nice to print something like:

  Merging with an empty tree,  'git clone' intended ?

I see more and more such messages when using various git commands, it
helps a lot.

  -- aghiles
--
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]