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

From: Aghiles <aghilesk@gmail.com>
Date: Apr 8, 2010, 19:46 UTC
Message-ID: <r2m3abd05a91004081246x35f9c674m6f4e379255513c80@mail.gmail.com>
In-Reply-To: <7v1veq8nyf.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 9 quoted lines

>
> ...
>
> 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