From: Marius Storm-Olsen <marius@trolltech.com>
To: simon@lst.de, gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Optimize the fetching of data from perforce.
Date: Tue, 04 Mar 2008 11:04:35 +0100 [thread overview]
Message-ID: <47CD1EB3.5030608@trolltech.com> (raw)
In-Reply-To: <1204624161-17691-1-git-send-email-marius@trolltech.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
Marius Storm-Olsen said the following on 04.03.2008 10:49:
> Signed-off-by: Marius Storm-Olsen <marius@trolltech.com>
> ---
> Huge speedup on Windows (a clone of ~43MB binary file is reduced from 5m 40s, to ~23s)
> No measureable impact on Linux for me.
Grr, the commit message was lost in 'translation' it seems. I'll
resend, and prefix "git-p4: " on the subject.
--
.marius
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
parent reply other threads:[~2008-03-04 10:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1204624161-17691-1-git-send-email-marius@trolltech.com>]
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=47CD1EB3.5030608@trolltech.com \
--to=marius@trolltech.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=simon@lst.de \
/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).