>> If there's a screwup, and you need to recut the branch, you want to be
>> sure someone else hasn't been helpful and added something else to the
>> repo.
>
> But you can put the tag/create the branch in any revision you want...
Suppose you have three subsequent revisions in the trunk:
A contains what you originally wanted to tag
A+1 contains a change by somebody else, not to be released
A+2 is the change that you made to fix a bug you noticed
during the release
How do you create the release tag so that it contains change
sets A and A+2, but not A+1? (and no, creating a branch just for
the release is no option, because that means you have to copy all
the changes you made on the branch back to the trunk)
Regards,
Martin
_______________________________________________
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
