best way to organize clones

[Tim Schmielau]

Hi Chris,

I see you have merged several clones but not mine. I know you prefer looking at the cumulative diff instead of at the individual changesets. And I guess you might not be happy with the "improvements" I made, even though I consider the "fixes" both important and trivial.

Would it be better if I divided the changes into two separate branches, one for fixes and one for improvements? That way any concern about the latter would not prevent the fixes from being merged as soon as possible.

Thanks,

Tim

[Christopher Lloyd]

Hey Tim,

First I would say I haven't had much time to integrate changes in a while, but I'll be dedicating some time to it going forward. I haven't even looked at the changes you've done so don't worry about that.

plasq's clone is the most active so it's important to integrate first, then I'll start cherry-picking other clones and doing some of my own work.

In general, since we all have our own clones for our own projects, it's not so critical changes go into the mainline quickly, you can always pull from someone else if you need the work. This can actually be helpful if you've reviewed the changes too.

Your current setup is okay!

Chris

[Tim Schmielau]

Thanks Chris!

I'm fine for my own needs, as I can easily apply my changes over whatever tree I'm using. I was just concerned about facilitating integration in general.