Re: [PATCH] Allow cloning an empty repository

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

 



Hi,

On Fri, 23 Jan 2009, Miklos Vajna wrote:

> On Fri, Jan 23, 2009 at 04:20:34AM +0100, Johannes Schindelin 
> <Johannes.Schindelin@xxxxxx> wrote:
>
> > But then, scripts have no business cloning repositories (fetching, 
> > yes.  But cloning?)
> 
> I think portals like repo.or.cz may do it.

"git grep git.clone" in repo.git suggests that only clonecheck.sh uses it, 
which is not called anywhere.

But more generally, the same should apply to such scripts as to human 
users: HTTP _is_ 2nd class, and the fetch _could_ succeed later.

> Isn't setting errno (or similar variable) in the HTTP code an option? 
> Then we could see why the transport failed and make a difference between 
> "network error" and "no refs found".

I'd rather see the HTTP code path taken by transport.c _fail_ (i.e. die()) 
when there is some sort of connection error.

Ciao,
Dscho

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

  Powered by Linux