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

Re: git cvsimport error

From
Adam Mercer <ramercer@gmail.com>
Date
May 23, 2008, 20:24 UTC
Message-ID
<799406d60805231324o209692d2o59a700024e52100c@mail.gmail.com>
In-Reply-To
<63BEA5E623E09F4D92233FB12A9F794301FC8BCA@emailmn.mqsoftware.com>
On Fri, May 23, 2008 at 3:05 PM, Craig L. Ching <cching@mqsoftware.com> wrote:
Show 5 quoted lines
> Yeah, I don't know much about it at all, but my advice would be to run
> cvsps by itself and generate a cache that git-fast-import can import.
> That's the approach we're taking because it gives us a chance to figure
> out where things have gone wrong as we have some bad, buggy commits in
> our archive (CVS created the bad commits).

I thought of using git-fast-import but the problem is that the CVS repository is still in use so I need to keep the git and CVS repos synchronised and it seems like git-fast-import can't be used in this case.

Cheers
Adam
Previous: Adam MercerNext: Shawn O. Pearce
Message 5 of 7 in “git cvsimport error”
  1. Adam MercerMay 21, 2008
  2. Adam MercerMay 21, 2008
  3. Craig L. ChingMay 21, 2008
  4. Adam MercerMay 23, 2008
  5. Adam MercerMay 23, 2008
  6. Shawn O. PearceMay 23, 2008
  7. Adam MercerMay 24, 2008

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.