From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Thu, 22 Jun 2006 19:36:00 GMT
Subject: Re: Incremental CVS update
Message-ID: <46a038f90606221236j2c5c9692yecef924aa769c1c9@mail.gmail.com>
In-Reply-To: <9e4733910606220526o14ebe76ala4d327f012a0e8f5@mail.gmail.com>

On 6/23/06, Jon Smirl <jonsmirl@gmail.com> wrote:
> cvsps keeps it's incremental status in ~/.cvps/*. parsecvs might want
> to keep it's status in the .git repository and use tags to locate it.
> You could even have a utility to show when and what was imported. By
> keeping everything in git it doesn't matter who runs the incremental
> update commands.

Jon,

what cvsps keeps is a cache of what it knows about the repo history,
to ask only for new commits. Now, cvsps will always write to STDOUT
the full history, and git-cvsimport discards the commits it has
already seen, based on reading the state of each git head.

So cvsps + git-cvsimport don't keep any extra data around, and I am
100% certain that parsecvs don't need that either.

cheers,


martin