This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients christian.heimes, eric.araujo, ezio.melotti, georg.brandl, jcea, loewis, orsenthil, pitrou, r.david.murray
Date 2013-03-14.07:26:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1363245987.31.0.752715291958.issue15917@psf.upfronthosting.co.za>
In-reply-to
Content
Reviewed the patch - the logic looks okay to me - namely verifying that the changeset the merged with the next +0.1, 3.x branch or default.

I tested.

2.7 -> push -> success.
3.1 -> push -> fail -> merge to 3.2 -> fail -> merge to default -> success.

Looks like a good server-side hgrc hook to have.
History
Date User Action Args
2013-03-14 07:26:27orsenthilsetrecipients: + orsenthil, loewis, georg.brandl, jcea, pitrou, christian.heimes, ezio.melotti, eric.araujo, r.david.murray
2013-03-14 07:26:27orsenthilsetmessageid: <1363245987.31.0.752715291958.issue15917@psf.upfronthosting.co.za>
2013-03-14 07:26:27orsenthillinkissue15917 messages
2013-03-14 07:26:27orsenthilcreate