From: Johan Herland <johan@herland.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org, "Kristian Høgsberg" <krh@redhat.com>
Subject: Re: Builtin-clone?
Date: Tue, 19 Feb 2008 08:08:33 +0100 [thread overview]
Message-ID: <200802190808.33611.johan@herland.net> (raw)
In-Reply-To: <alpine.LNX.1.00.0802182341430.5816@iabervon.org>
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/
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...
Have fun! :)
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2008-02-19 7:09 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 ` Johan Herland [this message]
2008-02-19 16:02 ` Builtin-clone? Kristian Høgsberg
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=200802190808.33611.johan@herland.net \
--to=johan@herland.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--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).