git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Incremental CVS update

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 22, 2006, 19:36 UTC
Message-ID
<46a038f90606221236j2c5c9692yecef924aa769c1c9@mail.gmail.com>
In-Reply-To
<9e4733910606220526o14ebe76ala4d327f012a0e8f5@mail.gmail.com>
On 6/23/06, Jon Smirl <jonsmirl@gmail.com> wrote:
Show 5 quoted lines
> 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
Previous: Jon SmirlNext: Jon Smirl
Message 2 of 3 in “Incremental CVS update”
  1. Jon SmirlJun 22, 2006
  2. Martin LanghoffJun 22, 2006
  3. Jon SmirlJun 22, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.