From: Keith Packard <keithp@keithp.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: keithp@keithp.com, Pavel Roskin <proski@gnu.org>,
git <git@vger.kernel.org>
Subject: Re: parsecvs and unnamed branches
Date: Sat, 17 Jun 2006 10:13:16 -0700 [thread overview]
Message-ID: <1150564396.6983.73.camel@neko.keithp.com> (raw)
In-Reply-To: <9e4733910606162251i65021336m4388d4da715befc9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Sat, 2006-06-17 at 01:51 -0400, Jon Smirl wrote:
> Have you checked parsecvs on the 38 test repositories in the cvs2svn source?
Those all run to completion without significant error (there are a
couple of tests with invalid symbol names that currently elicit errors).
I haven't validated that the imports are correct though; spot checks
seem to indicate that the problems encountered during the cvs2svn
development aren't the same as the problems we're finding.
--
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-17 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 21:44 parsecvs and unnamed branches Jon Smirl
2006-06-16 22:19 ` Keith Packard
2006-06-16 22:28 ` Jon Smirl
2006-06-16 22:39 ` Jon Smirl
2006-06-16 22:51 ` Keith Packard
2006-06-17 3:02 ` Jon Smirl
2006-06-17 3:12 ` Pavel Roskin
2006-06-17 3:31 ` Jon Smirl
2006-06-17 4:08 ` Pavel Roskin
2006-06-17 4:15 ` Jon Smirl
2006-06-17 4:35 ` Pavel Roskin
2006-06-17 5:30 ` Keith Packard
2006-06-17 5:51 ` Jon Smirl
2006-06-17 17:13 ` 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=1150564396.6983.73.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
--cc=proski@gnu.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).