Trond Norbye wrote: > > I am part of a team at Sun working on enhancing Memcached, and we do > need a place to store our changes while we're waiting for them to be > integrated into the official Subversion repository for Memcached. > > I asked on the memcached mailing lists on how external parties should > do their development (the repository is in Subversion and not well > suited for distributed work), and the community responded back that we > should create our own repository and put our changes there (and of > course push them out to the community ;-)) > > Could someone please create a Mercurial repository for us in the Web > Stack project?
Creating it is easy enough, we can certainly do that. I'd like to see some detail on how you'll be managing the differences that build up between the repositories? In the current sfw src model the upstream tarballs are kept as-is and there are a limited number of patches (ideally zero) which are applied at build time. This is kind of a pain, but it has the benefit of clearly tracking each distinct patch. As a side effect, it also discourages changes that aren't absolutely needed. If you do all the work on a private repository it'll be easier to introduce more change "while I'm editing this file". Ideally all the components are identical to the upstream tarball, so more change == bad. It also makes it a bit more work to track individual patches (for submitting upstream) since there might be unrelated changes to the same file so just running a diff won't give you the correct patch for a single bug. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
