Thomas Wouters schrieb: > On 9/27/07, Eric Smith <eric+python-dev at trueblade.com> wrote: >> >> Thomas Wouters wrote: >> >> > Unfortunately, that's not how it works :-) If you check something into >> > the trunk, it will be merged into Py3k sooner or later. I may ask the >> > original submitter for assistance if it's incredibly hard to figure out >> > the changes, but so far, I only had to do that with the SSL changes. The >> > decimal changes are being merged as I write this (tests running now.) Is >> > there anything in particular that needs to be done for decimal in Py3k, >> > besides renaming __div__ to __truediv__? >> > >> > If you re-eally need to check something into the trunk that re-eally >> > must not be merged into py3k, but you're afraid it's not going to be >> > obvious to the merger, please record the change as 'merged' using >> > "svnmerge merge -M -r<revision>". Please take care when picking the >> > revision ;) You can also just email me or someone else you see doing >> > merges, as I doubt this will be a common occurance. I think that the 'svnmerge block -r<revision>' command should be used. Or not? Thomas
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4