On Sun, Nov 2, 2008 at 19:03, Benjamin Peterson <[EMAIL PROTECTED]> wrote: > On Sun, Nov 2, 2008 at 6:05 PM, Brett Cannon <[EMAIL PROTECTED]> wrote: >> I have started the DVCS PEP which can be seen at >> http://docs.google.com/Doc?id=dg7fctr4_40dvjkdg64 . Not much is there >> beyond the rationale, usage scenarios I plan to use, and what other >> sections I plan to write. >> >> At this point I am looking for any suggestions for fundamental usage >> scenarios that I am missing from the PEP. If you think the few already >> listed are missing some core part of a VCS, please let me know. > > I think one very important requirement of Python's VCS is advanced > merging support. The trunk and py3k are very special branches because > a commit in one should not necessarily find its way into the other. To > that end, I think it's critical to have svnmerge.py-like blocking > (preferably with unblocking, too) and fine cherry-picking of > revisions. >
Add the blocking to the backport scenario. -Brett _______________________________________________ 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
