From: Junio C Hamano <junkio@cox.net>
To: "Lukas Sandström" <lukass@etek.chalmers.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-pack-redundant: speed and memory usage improvements
Date: Tue, 20 Dec 2005 13:02:50 -0800 [thread overview]
Message-ID: <7virtjh479.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <43A86422.3090909@etek.chalmers.se> (Lukas Sandström's message of "Tue, 20 Dec 2005 21:05:54 +0100")
Lukas Sandström <lukass@etek.chalmers.se> writes:
> This might be post-1.0 material, but I have tested it on a couple of
> different repositories and it appears to work as before, only faster
> and using less memory.
Thanks.
I had an impression that somehow we already had this slabbish
allocation but apparently we didn't.
Any particular area you have worries/uncertainty about, that
makes you mark this post-1.0?
next prev parent reply other threads:[~2005-12-20 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 20:05 [PATCH] git-pack-redundant: speed and memory usage improvements Lukas Sandström
2005-12-20 21:02 ` Junio C Hamano [this message]
2005-12-20 21:26 ` Lukas Sandström
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=7virtjh479.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=lukass@etek.chalmers.se \
/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).