Skip to main content

Import CVS project into existing Subversion repository

svn repository
You may know that I've migrated from an RCS system to a Subversion (SVN) version control system. I migrated our RCS archive into a stand-alone, read-only, svn repository for reference purposes (using cvs2svn --use-rcs) and copied all the files I personally needed into its own project folder in svnrepo/trunk/myproject. Since then I've been trying to get others to make the switch too.

The other day, a colleague asked if I could transfer his files. He had kept using RCS after my import, so I tried to import his project into a separate folder off the main svnrepo trunk. I figured cvs2svn would let me set a destination directory. Well... it doesn't.

I had a little discussion on the cvs2svn Mailing List. I thought it was my fault or ignorance. Turns out that you can't directly import a project into a specific svnrepo sub folder. And while it could be built, you have to realize something:
The entire import would come chronologically after everything up to that point. All tags, branches and comments would be "moved" to the moment of import, regardless of their original commit.

If that is ok, or something you can live with, compared to not having the project inside your main svnrepo, that's fine too and you can go ahead. You'll still need to write the function though.

There is a work-around too, though, although it is a bit more involved. It converts your RCS repo to a new, separate svn repo. You checkout those files again and svn add or svn import those into the main svn repo, where you'd like them.
Labels:

Comments

Post a Comment

Popular posts from this blog

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.
1 comment
Read more

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries 20 seconds time to live for negative entries 66254 cache hi...
2 comments
Read more

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .
2 comments
Read more