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

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

To: GENI Project Users <geni-users@emulab.net>, Admins of Emulab-derived Testbeds <testbed-admins@flux.utah.edu>, Testbed Developers list <testbed-dev@flux.utah.edu>, ProtoGENI Developers <geni-dev@emulab.net>
From: Robert P Ricci <ricci@cs.utah.edu>
Subject: [Testbed-admins] Methods for managing local changes to Emulab source code
Date: Mon, 7 Dec 2009 16:14:19 -0700

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!

Follow-Ups:
- Re: [Testbed-admins] Methods for managing local changes to Emulab source code
  - From: Kevin Atkinson <kevina@cs.utah.edu>
- Re: [Testbed-admins] [geni-dev] Methods for managing local changes to Emulab source code
  - From: Pat Gunn <pgunn@cs.cmu.edu>
- Re: [Testbed-admins] Methods for managing local changes to Emulab source code
  - From: Jonathan Walsh <jonathan.d.walsh@lmco.com>

Prev by Date: Re: [Testbed-admins] VLAN creation failed with Cisco 2960
Next by Date: Re: [Testbed-admins] Methods for managing local changes to Emulab source code
Previous by thread: Re: [Testbed-admins] VLAN creation failed with Cisco 2960
Next by thread: Re: [Testbed-admins] Methods for managing local changes to Emulab source code
Index(es):
- Date
- Thread