>> As already mentioned in this thread, a capability similar to what svn >> or cvs offers would be sufficient. > > That capability presented by centralised VCSen is entirely dependent on > the fact that they *are* centralised. Using a distributed VCS means the > same capability doesn't apply.
Why do you say that? People have demonstrated the contrary already. >> I'm not sure what point you are trying to make > > That I disagree with your position. You seem to think that the problem > has an obvious solution, which is not true; and that choice of a > distributed VCS should be delayed until the problem is solved, which I > don't agree with. But is *has* an obvious solution. See the implementation from Dj Gilcrease, or the spec that I just posted. > Your guess is incorrect; I've been bitten time and again by this problem > in many different contexts, enough to know that it's not obvious what > the “right” solution is. The configuration options of svn have served us well enough. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
