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

Moving a 5 person dev team from CVS to git

From
FGFrancis Galiegue <fg@one2team.net>
Date
Oct 19, 2008, 19:27 UTC
Message-ID
<200810192127.55954.fg@one2team.net>
Hello,

I work for a software company with a dev team of 5, and right now a CVS repository is used for all the code which covers 8 years of history among 52 modules and 1.6 GB data.

All devs use Eclipse, and its featureful CVS plugin. As for myself, I also write to the CVS tree, but in a CVS-to-git-to-CVS cycle (I don't use Eclipse but command line). I have talked about git, shown some of its capabilities, and my boss agreed to give it a shot, but with the following conditions:

* it must provide CVS access (branching and tagging included), as a transition 
measure;
* there must be an Eclipse plugin.

I have successfully imported all CVS modules into an equivalent number of git repositories so far. Unfortunately, I have two problems:

* the git-cvsserver does not support branching and tagging;
* I have successfully built the Eclipse plugin (Java 6, Eclipse 3.4), but am 
unable to make it clone a repository and see it in a project, despite quite a 
few hours googling around (it _does_ clone, I see the repo in the workspace; 
but it's invisible within Eclipse).

Is branching and tagging support a planned feature for git-cvsserver? Also, is there a step-by-step guide on using egit to clone an existing repository? (I'm a total beginner with Eclipse, so it may well be that I need to google some more.)

Thanks,
-- 
fge
Next: Shawn O. Pearce
Message 1 of 2 in “Moving a 5 person dev team from CVS to git”
  1. Francis GaliegueOct 19, 2008
  2. Shawn O. PearceOct 19, 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.