Hi Mike, > >I wonder how the guys who work on larger projects handle that (since I > >doubt that they don't have local copies of their CVS repositories). > > Martin, > They download tarballs of their repository, and install them on their local > machine. This is usually only for backup purposes. I doubt this will be a > useful strategy for most of us, as our repository will exceed 500MB within > the next couple of weeks. True - especially for my connection - if I start downloading it now, I might have the repository by the end of the week ;-)
> Maintaining two will be tough, but here is how I would do it. > > First, export your current repository. Then import it into your devel/hejl > tree. That's the easy part. > > Maintenance: > Check out a local copy of your leaf sf devel/hejl tree. > Do your normal updates in your local cvs repository. > When you're ready to update the sf repository, export both the SF and your > local repository. > Perform a diff on the two trees. > Copy all new/changed files to from your local export to your checked out SF > tree. > Now add all the new files, and commit the updated SF tree. > > This is a lot of work. Indeed, that's what it sounds like. I think I'll read up on CVS a little more (so at least I have a rough idea of what I'm doing) and then see wether I should just make SF my "main" repository, and use my local one as a backup (and so, being able to take care of all the sync problems locally). But again, before moving to SF, I'd like to have a better feel for what I'm doing with CVS, so I don't mess anything up. I just thought I'd ask, if there'd been an easy way to do what I had in mind, that would have been nice. Thanks for the feedback. Martin _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
