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

From: Aghiles <aghilesk@gmail.com>
Date: Apr 8, 2010, 02:43 UTC
Message-ID: <h2g3abd05a91004071943g6352370fnc68b81c73a204bb0@mail.gmail.com>
In-Reply-To: <4BBD3A98.2020207@drmicha.warpmail.net>

Show 11 quoted lines

> Aghiles venit, vidit, dixit 08.04.2010 09:56:
>> Hello,
>>
>> I mistakenly pulled a project into another project. I had the
>> "warning: no common commits" but the pull did proceed.
>> I am wondering if, from a usability point of view, it would be
>> best to avoid doing so by default.
>
> Puleeezze: No animals were harmed during the process, right? I mean, no
> data loss, all you have to do is a git reset. Let's try and not make Git
> into "Are you sure"dom.

How many times did you see that message? If you saw it, it was probably a mistake. I think that it is a safe bet to assume that whoever does that won't complain to type something like: git pull --no-common-commits-ok

I manage many git projects and this happens from time to time, mainly because of tiredness. I simply consider the proposed behaviour more natural.

Git is not the bare bone tool set anymore, it aspires into becoming a user friendly tool, usable by "the masses". And don't worry, following some simple usability rules won't make git less "cool".

Now, that was just a suggestion,

  -- aghiles