From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Kristian Høgsberg" <krh@redhat.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Daniel Barkalow <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: Re: [PATCH] builtin-clone: Implement git clone as a builtin command.
Date: Wed, 12 Dec 2007 18:24:18 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0712121823090.27959@racer.site> (raw)
In-Reply-To: <1197471866.9269.2.camel@hinata.boston.redhat.com>
Hi,
On Wed, 12 Dec 2007, Kristian H?gsberg wrote:
> On Wed, 2007-12-12 at 11:12 +0000, Johannes Schindelin wrote:
>
> > On Tue, 11 Dec 2007, Junio C Hamano wrote:
> ...
> > > * --shared optimization
> > >
> > > This is a very easy addition to "git remote add". You make sure
> > > that the added remote repository is on a local machine, and set
> > > up alternates to point at its object store.
> >
> > Concur.
> >
> > Since I want to lose that dependency on cpio on Windows (which we fake
> > by using tar), I'll implement this in C anyway.
>
> It's not used for --shared (which is just writing an alternates file),
> it's used for -l, hardlinking locally cloned repos. The code to replace
> cpio is already in the patch I sent, look for clone_local().
Sorry, that comment should have gone after another part of the original
message.
My only two excuses are that I am ill, and am overloaded with work.
Ciao,
Dscho
next prev parent reply other threads:[~2007-12-12 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 19:57 [PATCH] builtin-clone: Implement git clone as a builtin command Kristian Høgsberg
2007-12-11 20:59 ` Daniel Barkalow
2007-12-11 23:38 ` Kristian Høgsberg
2007-12-12 3:12 ` Junio C Hamano
2007-12-12 3:20 ` Junio C Hamano
2007-12-12 11:12 ` Johannes Schindelin
2007-12-12 15:04 ` Kristian Høgsberg
2007-12-12 18:24 ` Johannes Schindelin [this message]
2007-12-12 15:24 ` Kristian Høgsberg
2007-12-12 18:00 ` Daniel Barkalow
2007-12-12 18:25 ` Kristian Høgsberg
2007-12-12 18:40 ` Daniel Barkalow
2007-12-24 1:52 ` J. Bruce Fields
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=Pine.LNX.4.64.0712121823090.27959@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=krh@redhat.com \
/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).