> Work has been started on that, thanks! Roundup should soon support the > workflow described in the devguide for feature work, which will be awesome. Make sure to submit issues to the meta tracker, please. > I’ve tried to use a clone with a named branch for > http://bugs.python.org/issue5845 and found those bugs: > - The revset code is not robust against an hyphen in the branch name. Ok, I'll investigate. Not sure whether the revset syntax even supports that, though. > - The first patch was empty (note that the repo was not up to date). This I don't understand. What repo was not up to date? > - After pulling, merging and pushing, the patch created contained the > merge diff, not the useful diff with my changes. Again, please elaborate. What is the "merge diff" that it contained? > Another thing to make it rock more: In the repo list, use “#” instead of > “:” as a separator between repo URI and branch name; it’s standard > Mercurial form and will allow people to copy-paste the whole thing to > get a clone of the repo up to that branch. Ok, committed. Regards, Martin
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