Re: I have end-of-lifed cvsps
- From
Jakub Narębski <jnareb@gmail.com>
- Date
- Dec 18, 2013, 00:02 UTC
- Message-ID
- <CANQwDwdQZGhR=hhFHe7wRAeNej_F5fHspN7+f-LiJu06utwC-w@mail.gmail.com>
- In-Reply-To
- <20131217210255.GA18217@thyrsus.com>
On Tue, Dec 17, 2013 at 10:02 PM, Eric S. Raymond <esr@thyrsus.com> wrote:
Show 7 quoted lines
> Jakub Narębski <jnareb@gmail.com>: >> >> Errr... doesn't cvs-fast-export support --export-marks=<file> to save >> progress and --import-marks=<file> to continue incremental import? > > No, cvs-fast-export does not have --export-marks. It doesn't generate the > SHA1s that would require. Even if it did, it's not clear how that would help.
I was thinking about how the following part of git-fast-export `--import-marks=<file>`
Any commits that have already been marked will not be exported again. If the backend uses a similar --import-marks file, this allows for incremental bidirectional exporting of the repository by keeping the marks the same across runs.
How cvs-fast-export know where to start exporting from in incremental mode?
BTW. does cvs-fast-export support incremental *output*, or does it perform also incremental *work*?
Anyway, that might mean that generic fast-import stream based incremental (i.e. supporting proper thin fetch) remote helper is out of question, perhaps writing one for cvs / cvs-fe would bring incremental import from CVS to git?
-- Jakub Narebski