Re: [PATCH] clone: add --perm option to clone an shared repository
- From
- Roy Lee <roylee17@gmail.com>
- Date
- Jun 28, 2009, 14:30 UTC
- Message-ID
- <6eac7f470906280730pa22b63fh464cd79a76fa20b3@mail.gmail.com>
- In-Reply-To
- <4A3F5AC0.20207@gnu.org>
Hi,
On Mon, Jun 22, 2009 at 6:19 PM, Paolo Bonzini<bonzini@gnu.org> wrote:
Show 28 quoted lines
> 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?