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

Forking a CVS project

From
TKThomas Koch <thomas@koch.ro>
Date
Apr 13, 2008, 08:19 UTC
Message-ID
<200804131019.43201.thomas@koch.ro>
Good day everybody,
I'm a new disciple of GIT and eager to learn.

My current problem is, that I'd like to track an old CVS project and make my own fork via GIT. The CVS project in question is horde[1]. My first attempt looked like:

mkdir horde cd horde export CVSROOT=":pserver:cvsread@anoncvs.horde.org:/repository" git-cvsimport -v -C. .

But this did not work. I only got millions of lines like
WARNING: file /repository/horde/templates/index/frames_index.inc doesn't match 
strip_path /repository/CVSROOT/cfg.p. ignoring
So I imported each module separately:

MODULES="agora ansel chora ..."

for MODULE in $MODULES
do
    git-cvsimport -v -C$MODULE $MODULE
done

This took like 2 or 3 days and now I have one git repository for each module. But I'd rather have one big git repository containing all modules.

Could somebody give me a hint on how this could be achieved, please?

I also don't know CVS at all, because I started already with SVN. And I really don't want to learn CVS!

How do I keep track of the CVS repository after the import and merge the changes into my fork? Is there a way to not import the whole history, but to start my GIT repo with the current snapshot? Would that speed up the import?

[1] http://www.horde.org/source/using.php
Best regards,
-- 
Thomas Koch, Software Developer

Young Media Concepts GmbH
Sonnenstr. 4
CH-8280 Kreuzlingen
Switzerland

Tel    +41 (0)71 / 508 24 86
Fax    +41 (0)71 / 560 53 89
Mobile +49 (0)170 / 753 89 16
Web    www.ymc.ch
Message 1 of 1 in “Forking a CVS project”
  1. Thomas KochApr 13, 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.