From: Keith Packard <keithp@keithp.com>
To: Sean <seanlkml@sympatico.ca>
Cc: keithp@keithp.com, Nicolas Pitre <nico@cam.org>, git@vger.kernel.org
Subject: Re: observations on parsecvs testing
Date: Thu, 15 Jun 2006 15:04:28 -0700 [thread overview]
Message-ID: <1150409068.30681.134.camel@neko.keithp.com> (raw)
In-Reply-To: <20060615164742.570e33a0.seanlkml@sympatico.ca>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
On Thu, 2006-06-15 at 16:47 -0400, Sean wrote:
> las,
>
> That was a planned optimization which I did mention to Keith previously.
> Was kinda waiting to hear back how it was working for him, and if there
> was an interest to put more work into it to include in his mainline.
The rcs2git code is working great and is on 'master' at this point;
optimizations to generate all of the revisions in one pass would be
greatly appreciated.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-06-15 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 20:37 observations on parsecvs testing Nicolas Pitre
2006-06-15 22:03 ` Keith Packard
[not found] ` <20060615164742.570e33a0.seanlkml@sympatico.ca>
2006-06-15 20:47 ` Sean
2006-06-15 20:55 ` Nicolas Pitre
2006-06-15 22:04 ` Keith Packard [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=1150409068.30681.134.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=seanlkml@sympatico.ca \
/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).