On Mon, Jan 03, 2011 at 05:10:26PM +0000, corvid wrote:
Fredrik wrote:
On Mon, Jan 03, 2011 at 12:54:09PM -0300, Jorge Arellano Cid wrote:
* Can corvid make another repo in the same server? (e.g. for the port to fltk-1.3)
Isn't it better to just make an other branch in the same repo? Can't everybody with commit access do that? That should make bug fix sharing easier, right?
How much does that complicate usage? Is it pretty much 1) name a new branch and 2) use the same hg commands as usual but add some branch argument?
I would go with a separate repo for fltk-1.3 development. It's still a branch, so we can use 3-way merging to keep things in sync with mainline. The only difference is that you don't get fltk-1.3 development stuff automatically when cloning the main repo - which I think is a good thing. Once it's ready we pull it over in the main repo. That's the same procedure we used for the CSS-experimental branch. Cheers, Johannes