public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Francis Galiegue <fg@one2team•net>
To: git@vger•kernel.org
Subject: Moving a 5 person dev team from CVS to git
Date: Sun, 19 Oct 2008 21:27:55 +0200	[thread overview]
Message-ID: <200810192127.55954.fg@one2team.net> (raw)

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

             reply	other threads:[~2008-10-19 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19 19:27 Francis Galiegue [this message]
2008-10-19 20:20 ` Moving a 5 person dev team from CVS to git Shawn O. Pearce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200810192127.55954.fg@one2team.net \
    --to=fg@one2team$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox