git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristian Høgsberg" <krh@redhat.com>
To: Johan Herland <johan@herland.net>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: Builtin-clone?
Date: Tue, 19 Feb 2008 11:02:32 -0500	[thread overview]
Message-ID: <1203436952.32036.5.camel@gaara.boston.redhat.com> (raw)
In-Reply-To: <200802190808.33611.johan@herland.net>

On Tue, 2008-02-19 at 08:08 +0100, Johan Herland wrote:
> On Tuesday 19 February 2008, Daniel Barkalow wrote:
> > I remember some discussion of what was still needed in order to make clone 
> > a trivial caller of init, config, fetch, and (optionally) checkout, and 
> > that there was still something. But has anyone actually written the bulk 
> > of builtin-clone.c?
> 
> I remember Kristian Høgsberg posted some WIP back in December:
> http://thread.gmane.org/gmane.comp.version-control.git/67915/

What Johan said :)  I posted the patch in progress during the 1.5.4
freeze, and threatened to pick it up again in January after 1.5.4 was
released.  I haven't worked on it since, unfortunately.  It does most of
the option parsing and the local clone optimizations, but doesn't use
fetch correctly (as Daniel points out in the thread above).

Daniel, I'm pretty sure you have a better understanding of the fetch and
checkout side of clone, so if you want to take the patch and finish
those parts, I'm fine with that.

> I recently sent him (and the list) an email asking about his progress (and - 
> once his work arrives - whether it's a good idea to make 'git clone' 
> produce packed refs), but I have yet to hear from him...

I think packed refs in clone sounds like a good idea, but my primary
goal was really to just port it to C and avoid changes in behavior
during that work.

cheers,
Kristian

      reply	other threads:[~2008-02-19 16:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19  5:30 Builtin-clone? Daniel Barkalow
2008-02-19  7:08 ` Builtin-clone? Johan Herland
2008-02-19 16:02   ` Kristian Høgsberg [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=1203436952.32036.5.camel@gaara.boston.redhat.com \
    --to=krh@redhat.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=johan@herland.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 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).