See Interfaces, frontends, and tools page on Git Wiki, in “Tools”, “Interaction with other Revision Control Systems”, “Other”. There you would find a description and a link to rcs-fast-export (gitweb) Ruby script by Giuseppe “Oblomov” Bilotta. (Web search would find also Ohloh page and announcement for mentioned project).
A ‘dummy’ update will give you this information. cvs -qn update A short description of the used options: -q Cause CVS to be somewhat quiet. -n Do not execute anything that will change the disk.
I’ve used both. There is no comparison; you want svn. The only reason to use CVS is because you are entering or taking over a legacy system with management that does not want to change the status quo. If you are starting on a new project, it is virtually a logical impossibility to argue that … Read more
You use cvs update -C filename
I suppose this command would help: cvs diff -N -c -r RELEASE_1_0 -r RELEASE_1_1 > diffs where RELEASE_1_0 and RELEASE_1_1 are the names of your tags. You can find a little more information on cvs diff command here plus it should be fairly simple to create a script to make report more suitbable for your … Read more
The only tool that has incremental import seems to be git-cvsimport. If you want to convert (migrate) from CVS to Git, the best solution for now seems to be mentioned above cvs2git mode of cvs2svn. See also Interfaces Frontends And Tools page on Git wiki, section about interaction with other revision control systems.
CVS only tracks modification on a file-by-file basis, while SVN tracks a whole commit as a new revision, which means that it is easier to follow the history of your project. Add the fact that all modern source control software use the concept of revision so it is far easier to migrate from SVN than … Read more
I recently wrote up a utility to statically check the syntax of SQL for PostgreSQL. It leverages ecpg, the embedded SQL C preproccessor for postgres, to check the SQL syntax, so it uses the exact same parser that is built in to Postgres itself. You can check it out on github: http://github.com/markdrago/pgsanity. You can give … Read more
To simply create a diff patch in git’s diff format from two arbitrary files or directories, without any fancy repository stuff or version control: git diff –no-index some/path other/path > some_filename Jakub Narębski’s comment on knittl’s answer hinted at the answer… For simplicity’s sake, that’s the full command. The > part creates a file and … Read more
Fortunately for those of us who are still forced to use CVS, git provides pretty good tools to do exactly what you’re wanting to do. My suggestions (and what we do here at $work): Creating the Initial Clone Use git cvsimport to clone the CVS revision history into a git repository. I use the following … Read more