Re: [RFC] Moving "git remote add --mirror blah" functionality to "git clone --bare --origin=blah"

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

 



Hi,

On Wed, 23 Apr 2008, Paolo Bonzini wrote:

> In the thread "git remote update -> rejected" Junio and Johannes came to 
> the conclusion that "--mirror means that you do not have local 
> branches", because "you give control away to the other end on the ref 
> namespace".  Furthermore, it was agreed that --mirror currently makes 
> sense mostly (or only?) on a bare repository.

Yes.  But the opposite may not be true: if you plan to work on many 
workdirs, but the same repository, you might still want to have separate 
remotes layout.

In any case, I think that this discussion is too early: clone should be 
builtin first, making things much simpler because of being a very thin 
layer on top of init && remote && fetch.

But yes, there is a lot of work left on the builtin-clone to make it so.

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