Mercurial and Agile

[Smith, Michael]

In my day job we do this with CVS. But that works because all our commits have meta data specific to our operations embeded in them. The tool which imports changes between branches looks at meta data and decides which changes to bring across. The meta data also traces to information about dependencies between changes. I have written versions of this tool which work with mercurial but they rely on having our meta data in place. In fact importing between branches in CVS is not too different from importing between repos in hg.



DISCLAIMER:---------------------------------------------------------------------------
This e-mail transmission and any documents, files and previous e-mail messages
attached to it are private and confidential. They may contain proprietary or copyright
material or information that is subject to legal professional privilege. They are for
the use of the intended recipient only.  Any unauthorised viewing, use, disclosure,
copying, alteration, storage or distribution of, or reliance on, this message is
strictly prohibited. No part may be reproduced, adapted or transmitted without the
written permission of the owner. If you have received this transmission in error, or
are not an authorised recipient, please immediately notify the sender by return email,
delete this message and all copies from your e-mail system, and destroy any printed
copies. Receipt by anyone other than the intended recipient should not be deemed a
waiver of any privilege or protection. Thales Australia does not warrant or represent
that this e-mail or any documents, files and previous e-mail messages attached are
error or virus free.
--------------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090702/6025889b/attachment.htm