From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Re: [PATCH] Use adler32() from zlib instead of defining our own.
Date: Sun, 5 Feb 2006 00:20:23 +0100 [thread overview]
Message-ID: <20060204232023.GA25081@ebar091.ebar.dtu.dk> (raw)
In-Reply-To: <20060204225401.GA24725@ebar091.ebar.dtu.dk>
On Sat, Feb 04, 2006 at 11:54:01PM +0100, Peter Eriksen wrote:
>
> Since we already depend on zlib, we don't need to define our
> own adler32(). Spotted by oprofile.
Sorry for the bad formatting, I don't use git-format-patch often enough
to be comfortable with it yet.
The patch shows no regression on my machine and at least doesn't slow
down the 2.6.15 merge with 2.6.12+change, but I don't know, if it's
correct. It just seemed like an easy cleanup.
It was only spotted indirectly, while I was playing with OProfile
(thanks Linus), trying to find the bottlenecks in the afore mentioned
merge.
Regards,
Peter
prev parent reply other threads:[~2006-02-04 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 22:54 [PATCH] Use adler32() from zlib instead of defining our own Peter Eriksen
2006-02-04 23:20 ` Peter Eriksen [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=20060204232023.GA25081@ebar091.ebar.dtu.dk \
--to=s022018@student.dtu.dk \
--cc=git@vger.kernel.org \
/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).