Re: [PATCH] clone: add --perm option to clone an shared repository

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

 



Hi,

On Mon, Jun 22, 2009 at 6:19 PM, Paolo Bonzini<bonzini@xxxxxxx> wrote:
> Johannes Schindelin wrote:
>>
>> Hi,
>>
>> On Mon, 22 Jun 2009, Paolo Bonzini wrote:
>>
>>> Roy Lee wrote:
>>>>
>>>> The term 'shared' used here is in the same context with git init.
>>>> Unfortunately the 'shared' option has been taken, so I took the "perm"
>>>> as a place holder in this patch. Any comments?
>>>
>>> I think it would make sense to add "perm" to git-init too (and possibly
>>> deprecate --shared).
>>
>> Agreed.  After we teach everybody on this planet that "perm" means
>> "shared", and "shared" does not.
>
> Or instead of teaching everybody on this planet that "shared" means "set
> permissions for sharing" in one context, and "use hard links and set up
> .git/objects/info/alternates, which by the way may be dangerous" in another.
> :-)
>
> But you made me think, and maybe it is better to remove argument-less
> --shared instead.  What Roy introduced seems much more useful in practice.
>
> Paolo
>

This patch intends to provide the functionality for git clone to convert
existing repositories to "shared" ones.

Have we come to agreement to add such functionality?
If so, how do we get to the agreement on the used terms or other issues?
--
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]