Comments on: A Better Mirror http://iamthewalr.us/blog/2007/10/a-better-mirror/ by Colin Barrett Sun, 06 Jun 2010 00:19:02 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Colin http://iamthewalr.us/blog/2007/10/a-better-mirror/comment-page-1/#comment-13870 Colin Tue, 16 Oct 2007 15:10:51 +0000 http://iamthewalr.us/blog/2007/10/15/a-better-mirror/#comment-13870 <p>I don't think at this point that's really all that important.</p> <p>I don't think the general developing public is ever going to forward merge to Moz2. When we get enough people doing Moz2 stuff that that would become an issue, we'll be wanting to focus on Moz2 anyway, so we'll be backporting. Otherwise, Moz2 folks will be wanting to pull in changes from CVS anyway.</p> <p>It sucks if you're doing something that affects Moz2 **and** 1.9 **and** you want to share changesets between two local repositories, but I think the codebases and workflows are different enough already that there are other problems there. I think a more typical workflow would be to hack on Moz2, and then backport locally to 1.9.</p> <p>Overlay repositories are pretty much exactly what we want here, I think. Check out the Mercurial wiki page I linked in the article, you can try it out now.</p> <p>I agree though, that long term we want a better solution. Perhaps checking in a version of client.py, or let client.mk know how to deal with hg?</p> I don’t think at this point that’s really all that important.

I don’t think the general developing public is ever going to forward merge to Moz2. When we get enough people doing Moz2 stuff that that would become an issue, we’ll be wanting to focus on Moz2 anyway, so we’ll be backporting. Otherwise, Moz2 folks will be wanting to pull in changes from CVS anyway.

It sucks if you’re doing something that affects Moz2 **and** 1.9 **and** you want to share changesets between two local repositories, but I think the codebases and workflows are different enough already that there are other problems there. I think a more typical workflow would be to hack on Moz2, and then backport locally to 1.9.

Overlay repositories are pretty much exactly what we want here, I think. Check out the Mercurial wiki page I linked in the article, you can try it out now.

I agree though, that long term we want a better solution. Perhaps checking in a version of client.py, or let client.mk know how to deal with hg?

]]> By: Benjamin Smedberg http://iamthewalr.us/blog/2007/10/a-better-mirror/comment-page-1/#comment-13867 Benjamin Smedberg Tue, 16 Oct 2007 13:40:42 +0000 http://iamthewalr.us/blog/2007/10/15/a-better-mirror/#comment-13867 <p>One key advantage of cloning-merging from cvs-trunk-mirror is that changesets can be merged or transplanted fairly easily to mozilla-central... if you do a separate import, it will be an unrelated repository.</p> One key advantage of cloning-merging from cvs-trunk-mirror is that changesets can be merged or transplanted fairly easily to mozilla-central… if you do a separate import, it will be an unrelated repository.

]]>