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 ezio.melotti
Recipients christian.heimes, ezio.melotti, georg.brandl, jcea, loewis, pitrou
Date 2012-09-11.14:39:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347374366.83.0.784749555228.issue15917@psf.upfronthosting.co.za>
In-reply-to
Content
Attached a set up script to reproduce a test environment for the hook.

Create an empty dir and run ``sh setup.sh`` in it.  This will:
  1) create a 'c1' subdir which is a cpython-like repo with the branches 2.7, 3.1, 3.2, default;
  2) download and set up the hook for this repo; 
  3) create a 'c2' clone of 'c1';

Once the clones are created, cd in 'c2', try to commit something, and push it.

Use `hg up <branchname>` to switch between branches.

If you `hg up 3.1`, change something, commit, and push, the hook will tell you that you have to merge with 3.2, if you do the same on 3.2 it will say you have to merge with default.

You can try unusual combinations (e.g. null merges, rollbacks, multiple commits per branch, etc.) to see how well the hook works.
History
Date User Action Args
2012-09-11 14:39:26ezio.melottisetrecipients: + ezio.melotti, loewis, georg.brandl, jcea, pitrou, christian.heimes
2012-09-11 14:39:26ezio.melottisetmessageid: <1347374366.83.0.784749555228.issue15917@psf.upfronthosting.co.za>
2012-09-11 14:39:26ezio.melottilinkissue15917 messages
2012-09-11 14:39:25ezio.melotticreate