Re: git clone NonExistentLocation

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

 



Sverre Rabbelier venit, vidit, dixit 17.02.2011 15:03:
> Heya,
> 
> [Thanks for summarizing.]
> 
> On Thu, Feb 17, 2011 at 12:59, Michael J Gruber
> <git@xxxxxxxxxxxxxxxxxxxx> wrote:
>> Sverre, with your 86ac751, the following two are equivalent (modulo a
>> warning) on a nonexisting dir:
>>
>> git clone dir
>> git init dir
>>
>> Is that intentional?
> 
> No, that was not intentional. The former should still be an error if
> 'dir' is an empy directory.
> 

Digging a little further: since a nonexisting directory is neither a dir
nor a file, clone thinks it is not local (is_local=is_bundle=0). None of
the transport_* commands error out since the relevant one is guarded by
86ac751...

Reverting that or forcing is_local=1 both help, but how to detect "local
nonexisting" reliably?

In fact, I don't have a problem with the current state if we document it :)

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