Nathaniel Smith wrote:
There is also a theory that says it's more dangerous to keep it separate. If you want to minimize merging pain, you probably want to minimize how much divergence occurs, so the sooner it gets merged into mainline and new changes start being made against it instead of the old stuff, the less nasty merging will need to happen...?
The first thought I had here was for the new rosters restrictions branch and how much fun merging in the changes might be. So, are we in a state where we can consider merging in the new restrictions code? Has anyone looked at it? Does it look sane? ;)
I can dust it off and make sure things still work over the weekend or something.
Cheers, Derek _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel