From: "Lukas Sandström" <lukass@etek.chalmers.se>
To: Junio C Hamano <junkio@cox.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-pack-redundant: speed and memory usage improvements
Date: Tue, 20 Dec 2005 22:26:19 +0100 [thread overview]
Message-ID: <43A876FB.8020901@etek.chalmers.se> (raw)
In-Reply-To: <7virtjh479.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> 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?
>
No, as far as I can see, there should be no problems with the patch.
It is non-trivial though so, according to history, there might be
bugs that only show on certain repositories.
/Lukas
prev parent reply other threads:[~2005-12-20 21:25 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
2005-12-20 21:26 ` Lukas Sandström [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=43A876FB.8020901@etek.chalmers.se \
--to=lukass@etek.chalmers.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).