From: Keith Packard <keithp@keithp.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: keithp@keithp.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: Fixes to parsecvs
Date: Thu, 06 Apr 2006 10:36:19 -0700 [thread overview]
Message-ID: <1144344979.2303.263.camel@neko.keithp.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0604061723410.23681@wbgn013.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Thu, 2006-04-06 at 17:26 +0200, Johannes Schindelin wrote:
> Keep in mind that there are many more valid uses for tracking a CVS
> repository than to import it once.
Sure, but we should fix parsecvs to handle incremental CVS tracking if
that's one of the goals for this utility. git-cvsimport does this by
skipping commits earlier than a fixed time; if we did that, we'd
eliminate the huge memory usage except for initial imports. I haven't
considered how this might be done in detail yet; I have no personal need
for this functionality.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-06 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060405174247.GA29758@blackbean.org>
[not found] ` <1144262498.2303.231.camel@neko.keithp.com>
2006-04-06 6:36 ` Fixes to parsecvs Keith Packard
2006-04-06 12:08 ` Jan-Benedict Glaw
2006-04-06 14:48 ` Keith Packard
2006-04-06 15:26 ` Johannes Schindelin
2006-04-06 16:09 ` Jan-Benedict Glaw
2006-04-06 17:36 ` Keith Packard [this message]
2006-04-09 23:17 ` Francois Romieu
2006-04-06 18:15 ` parsecvs tool now creates git repositories Jim Radford
2006-04-06 20:12 ` Keith Packard
2006-04-06 21:51 ` Martin Langhoff
2006-04-06 22:19 ` Keith Packard
2006-04-06 23:22 ` Martin Langhoff
2006-04-07 7:24 ` Keith Packard
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=1144344979.2303.263.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=Johannes.Schindelin@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.