On Sat, Jul 4, 2009 at 00:37, Barry Warsaw<barry at python.org> wrote: > Doesn't Mercurial support an Subversion bridge? Would it be possible to > provide a /read-only/ copy of the hg branches for 2.4 (maybe), 2.5, 2.6, and > 3.1? If so, then the release managers would simply have to cut their > releases from the svn copy instead of the hg master. /All/ other work would > be done from the hg master. This shouldn't be too much of a burden since > it's done so rarely and would end with the EOL of each of those branches. There is some push support in hgsubversion, but it doesn't do tags at this time, for example. I think this setup would be needlessly complicated (and tools will need to learn the new revision specifier anyway, so why not have it learn them sooner rather than later)? Cheers, Dirkjan
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