From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] git-clone --shared should imply --local
Date: Tue, 29 Nov 2005 02:17:31 -0500 [thread overview]
Message-ID: <1133248651.27750.82.camel@dv> (raw)
In-Reply-To: <7viruclymo.fsf@assigned-by-dhcp.cox.net>
On Mon, 2005-11-28 at 23:08 -0800, Junio C Hamano wrote:
> Pavel Roskin <proski@gnu.org> writes:
>
> > The "--shared" option to git-clone is silently ignored if "--local" is
> > not specified. The manual doesn't mention such dependency. Make
> > "--shared" imply "--local".
> >
> > Signed-off-by: Pavel Roskin <proski@gnu.org>
>
> Hmph, then probably the manual should say it implies it...
Actually, from the user point of view --local and --shared are
alternatives to each other and to the default behavior. --local copies
files, --shared makes a reference.
Saying that --shared implies --local could sound like git-clone would
still copy all objects.
My description was from the implementation point of view.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2005-11-29 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 6:20 [PATCH] git-clone --shared should imply --local Pavel Roskin
2005-11-29 7:08 ` Junio C Hamano
2005-11-29 7:17 ` Pavel Roskin [this message]
2005-11-29 7:52 ` Junio C Hamano
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=1133248651.27750.82.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.