From: "Kristian Høgsberg" <krh@redhat.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Johan Herland" <johan@herland.net>,
git@vger.kernel.org, "Santi Béjar" <sbejar@gmail.com>
Subject: Re: [RFC] Build in clone
Date: Tue, 26 Feb 2008 13:53:35 -0500 [thread overview]
Message-ID: <1204052015.11329.5.camel@gaara.boston.redhat.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0802261128360.19024@iabervon.org>
On Tue, 2008-02-26 at 12:36 -0500, Daniel Barkalow wrote:
> On Tue, 26 Feb 2008, Johan Herland wrote:
>
> > Other than the failing tests, it seems to work fairly well. I've been
> > playing around with it for a few minutes, and on a test repo I have with
> > 1001 branches and 10000 tags, it cuts down the runtime of a local git-clone
> > from 25 seconds to ~1.5 seconds. (simply by eliminating the overhead of
> > invoking git-update-ref for every single ref) :)
>
> Good to hear. A certain amount of the point is performance, and I've only
> got relatively simple repositories on Linux to test with, where everything
> is too fast to tell anyway.
Yeah, that's pretty cool.
> > - Fix "clone from $repo" reflog messages (using strbufs; something tells
> > me more of this code would benefit from using strbufs)
>
> Most likely. I think Kristian wrote most of this before strbuf existed or
> something of the sort.
No this was after the strbuf API went in. The "clone from $repo"
messages I just left at the time because I was lazy, but yeah, they'll
need some strbuf love, or maybe just snprintf. I don't agree that
strbuf applies very well for the rest of the code. I'm a big fan of the
strbuf functionality, but I've been very deliberate about using and not
using it.
cheers,
Kristian
next prev parent reply other threads:[~2008-02-26 18:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 21:12 [RFC] Build in clone Daniel Barkalow
2008-02-26 2:21 ` Johan Herland
2008-02-26 11:14 ` Johannes Schindelin
2008-02-26 12:19 ` Johan Herland
2008-02-26 12:58 ` Johan Herland
2008-02-26 13:37 ` Johan Herland
2008-02-26 15:35 ` [PATCH] Fix premature free of ref_lists while writing temporary refs to file Johan Herland
2008-02-26 15:42 ` Johannes Schindelin
2008-02-26 17:17 ` Johan Herland
2008-02-26 23:07 ` Daniel Barkalow
2008-02-26 23:11 ` Johan Herland
2008-02-26 15:40 ` [PATCH] Fix premature call to git_config() causing t1020-subdirectory to fail Johan Herland
2008-02-26 15:47 ` Johannes Schindelin
2008-02-26 22:12 ` Daniel Barkalow
2008-02-26 22:40 ` Johannes Schindelin
2008-02-26 22:49 ` Daniel Barkalow
2008-02-27 0:20 ` Junio C Hamano
2008-02-27 0:53 ` Daniel Barkalow
2008-02-27 1:34 ` Junio C Hamano
2008-02-27 19:47 ` Daniel Barkalow
2008-02-27 20:09 ` Junio C Hamano
2008-02-27 20:31 ` Daniel Barkalow
2008-02-26 17:36 ` [RFC] Build in clone Daniel Barkalow
2008-02-26 18:53 ` Kristian Høgsberg [this message]
2008-03-02 5:57 ` [PATCH] builtin-clone: create remotes/origin/HEAD symref, if guessed Johannes Schindelin
2008-03-02 6:25 ` [PATCH, fixed] " Johannes Schindelin
2008-03-02 7:46 ` [PATCH] builtin clone: support bundles Johannes Schindelin
2008-03-02 16:19 ` Daniel Barkalow
2008-03-03 0:04 ` Santi Béjar
2008-03-02 16:48 ` Daniel Barkalow
2008-03-02 17:34 ` Johannes Schindelin
2008-03-02 17:50 ` Junio C Hamano
2008-03-02 17:54 ` Junio C Hamano
2008-03-03 9:04 ` [PATCH] Add test for cloning with "--reference" repo being a subset of source repo Johan Herland
2008-03-03 16:36 ` Daniel Barkalow
2008-03-03 18:21 ` Daniel Barkalow
2008-03-04 3:02 ` Johan Herland
2008-03-04 3:04 ` [PATCH 1/2] Add test illustrating issues with sha1_file_name() and switching repos Johan Herland
2008-03-04 3:05 ` [PATCH 2/2] Overly simplistic fix for issue " Johan Herland
2008-03-04 23:10 ` [PATCH] Add test for cloning with "--reference" repo being a subset of source repo Daniel Barkalow
2008-03-05 0:24 ` Daniel Barkalow
2008-03-05 23:56 ` Johan Herland
2008-03-03 17:05 ` [PATCH, fixed] builtin-clone: create remotes/origin/HEAD symref, if guessed Kristian Høgsberg
2008-03-03 17:09 ` Pierre Habouzit
2008-03-03 19:55 ` Johannes Schindelin
2008-03-03 17:10 ` Johannes Schindelin
2008-03-03 17:41 ` Johan Herland
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=1204052015.11329.5.camel@gaara.boston.redhat.com \
--to=krh@redhat.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=johan@herland.net \
--cc=sbejar@gmail.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).