-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alex Chapman wrote:
Log message for revision 113961: - branch for ZODB with bigger bucketswq
Changed: A ZODB/branches/3.9.0b5-patched/
I see a couple of issues here: - - Branches which are intended for feature development should be made from the trunk, not from a release tag. - - Branches which are intended for bug fixes should be made from the tip of the corresponding release branch. - - Branches / tags which do not correspond to release lines / releases should have the developer's ID included, so we know who to ask about the thing later. This looks like you want something which fits neither of these purposes: in essence, you want to use the 3.9.0b5 release for some reason, but want to apply a patch to Are you sure that you dont just want to use a buildout recipe which allows you to apply the patch? E.g.: http://pypi.python.org/pypi/collective.recipe.patch/0.2.2 http://pypi.python.org/pypi/minitage.recipe.egg/1.78 Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwqTc4ACgkQ+gerLs4ltQ6iXACg0/yvf6Auf9PHdjSQWNqoqDaH FAkAnj3MES8LCZN2FKsJiIvgK0XHQRkk =sKz5 -----END PGP SIGNATURE-----