From: Roy Lee <roylee17@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] clone: add --perm option to clone an shared repository
Date: Sun, 28 Jun 2009 22:30:26 +0800 [thread overview]
Message-ID: <6eac7f470906280730pa22b63fh464cd79a76fa20b3@mail.gmail.com> (raw)
In-Reply-To: <4A3F5AC0.20207@gnu.org>
Hi,
On Mon, Jun 22, 2009 at 6:19 PM, Paolo Bonzini<bonzini@gnu.org> 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?
prev parent reply other threads:[~2009-06-28 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-21 12:17 [PATCH] clone: add --perm option to clone an shared repository Roy Lee
2009-06-22 8:17 ` Paolo Bonzini
2009-06-22 9:34 ` Johannes Schindelin
2009-06-22 10:19 ` Paolo Bonzini
2009-06-28 14:30 ` Roy Lee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6eac7f470906280730pa22b63fh464cd79a76fa20b3@mail.gmail.com \
--to=roylee17@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bonzini@gnu.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).