[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Testbed-admins] Methods for managing local changes to Emulab source code



Robert P Ricci wrote:
I know that several of you maintain local changes to your Emulab source
tree, and occasionally sync up to our CVS. For those of you who do, can
you give me a quick summary of how you do it, and how well you think it
works?

We're looking at ways to make it easier for others to maintain local
changes, so I'd like to hear from anyone who has a solution that they
are (or aren't) happy with.

Thanks!
_______________________________________________
Testbed-admins mailing list
Testbed-admins@flux.utah.edu
http://www.flux.utah.edu/mailman/listinfo/testbed-admins

Rob,

For small purposeful changes (for example porting to FBSD7) I generally just install the latest version on my development hardware, do what I need to, then when it makes sense generate a patch file. This really only ever works when I am the only one working on a task.

For larger efforts we have a separate SVN repo that I very occasionally sync up with your CVS repo. I have some scripts to do this, but there are still some manual steps when there are significant conflicts. If you come up with a better way to do it, I'd love to hear it.

-Jonathan