Ah, I'm sorry, I misunderstood your question. Yes, that is a problem. I see no way around it in general. The only way to mitigate this is to try to avoid changing files that sage-combinat is working on. But I doubt that Sage developers want to commit to such a promise, unless sage-combinat wants to take ownership of parts of Sage... and certainly your objection applies to any broad changes to the Sage codebase. But what leif (I think) and I were trying to say is that at least this change he mentioned would be a lot easier to handle than other large-scale changes (such as, say, python3 migration changes which will eventually happen).
If I understand correctly, sage-combinat is an project which develops extensions of Sage which periodically (when sage-combinat feels a particular ticket is ready for review?) gets included into Sage itself. The standard way to do such a thing with Mercurial is to maintain a separate clone of the Sage repository (or a separate branch within the Sage repository), and merge changes from mainstream Sage into that repo every time Sage releases a new version. This way you don't need to muck about with rebasing multiple patch files etc., and pulling from the sage-combinat repo back into the mainstream Sage repo is relatively painless. In particular, I've never heard of anyone long-term sharing a patch queue repository and using it for development - that sounds really painful to me! (pre-posting edit: People in the IRC channel #mercurial on freenode said that they have heard of this workstyle but find it "quite painful" too...) However, sadly, Sage does not really properly use Mercurial in a nice way, i.e. nobody touches our repository except the release manager, and there are scripts to handle all of that, which only expect to be merging patches from trac tickets and not doing anything else. So it may be a bit difficult to implement a nicer way for sage-combinat to collaborate with Sage, at least at the moment... (As you may know, I am a very junior Sage developer so take what I say with a grain of salt, please :) ) -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
