Current patch process question

I am confused by the current hydra-like development. I've recently submitted a change (issue6422 -- a feature request) which is currently moving through the process. I am not particularly asking for special attention on that issue, but I am confused about the process I should be using (in the face of two trunks). There seem to be two places to plausibly introduce a change: py3k and trunk. Should I submit changes for trunk, py3k, or both? I tried asking in the initial feature request, but nobody replied, and I finally decided that I'd go for patching trunk in the interim. For myself, I'd like to know if I should add a patch file for the py3k branch, or will that simply make more work for someone else? Certainly it will be easier for me to do this sooner rather than later. For the wider group, how should I have known the answer to these questions? Is there some page I overlooked? Is there a better forum in which to ask this question? --Scott David Daniels Scott.Daniels@Acm.Org

Hi,
There seem to be two places to plausibly introduce a change: py3k and trunk. Should I submit changes for trunk, py3k, or both? I tried asking in the initial feature request, but nobody replied, and I finally decided that I'd go for patching trunk in the interim.
Patches are usually first checked into trunk, and then svnmerge'd to py3k. So it makes more sense to submit your patch against trunk.
For myself, I'd like to know if I should add a patch file for the py3k branch, or will that simply make more work for someone else?
If porting the patch to py3k is trivial, you shouldn't care. svnmerge will take care of it. If, on the other hand, porting your patch requires many changes, or delicate ones, providing a patch against py3k can make the committer's life easier. Regards Antoine.

There seem to be two places to plausibly introduce a change: py3k and trunk. Should I submit changes for trunk, py3k, or both? I tried asking in the initial feature request, but nobody replied, and I finally decided that I'd go for patching trunk in the interim.
Patches are usually first checked into trunk, and then svnmerge'd to py3k. So it makes more sense to submit your patch against trunk.
For myself, I'd like to know if I should add a patch file for the py3k branch, or will that simply make more work for someone else?
If porting the patch to py3k is trivial, you shouldn't care. svnmerge will take care of it. If, on the other hand, porting your patch requires many changes, or delicate ones, providing a patch against py3k can make the committer's life easier.
I usually abstain from "me too" messages, but only this time: as Antoine says. Regards, Martin

Martin v. Löwis wrote:
There seem to be two places to plausibly introduce a change: py3k and trunk. Should I submit changes for trunk, py3k, or both? .... Patches are usually first checked into trunk, and then svnmerge'd to py3k. So it makes more sense to submit your patch against trunk.
For myself, I'd like to know if I should add a patch file for the py3k branch, or will that simply make more work for someone else? If porting the patch to py3k is trivial, you shouldn't care. svnmerge will take care of it. If, on the other hand, porting your patch requires many changes, or delicate ones, providing a patch against py3k can make the committer's life easier.
I usually abstain from "me too" messages, but only this time: as Antoine says.
Thanks to both of you for the quick response. In this case, the port should be dirt simple, so I'll consider myself done until comments come back on the patch. --Scott David Daniels Scott.Daniels@Acm.Org
participants (3)
-
"Martin v. Löwis"
-
Antoine Pitrou
-
Scott David Daniels