From: Stefan Naewe <stefan.naewe@atlas-elektronik.com>
Date: Thu, 17 Feb 2011 12:52:20 GMT
Subject: Re: git clone NonExistentLocation
Message-ID: <4D5D1A04.4090107@atlas-elektronik.com>
In-Reply-To: <4D5D1715.5020707@drmicha.warpmail.net>

On 2/17/2011 1:39 PM, Michael J Gruber wrote:
> 
> It is useful, and it even gives you a warning that it still might not be
> what you intended. Would be funny if it were accidental. Indeed, a git
> "log -S" on that warning reveals that it was introduced intentionally in
> 
> 86ac751 (Allow cloning an empty repository, 2009-01-23)

OK. But that's about 'cloning an empty repository'.
'NonExistentLocation' is not empty initially - it simply does
not exist.

Contrast that to 'git clone http://url.does.not.exist'. You don't
get an empty repository in 'url.does.not.exist' after running that.

Regards,
  Stefan
-- 
----------------------------------------------------------------
/dev/random says: ==/==/==/==Police tagline==/==/==Do not cross ==/==/==/==