Yes, i used it quite often recent times. Usually I have a local copy of the repository and I do commits pretty often just to be able to revert if something goes wrong. Some of these commits are too small to be left in the final history. So after some feature is ready I update to some earlier revision (before this feature was started) and do reverts to some intermediate revisions and committing to a new unnamed branch. The original unnamed branch isstripped after that.
I understand that it is 'history editing' and it is not widely approved but all these things do not go out from my copy of the repository and I found the revert capability quite useful. Something similar could be achieved with MQ or pbranch but MQ will concatenate the commit messages when merging different patches and pbranch, I believe, is still non-functional in PyQT version of THg. Oleg. Thu, 10 Feb 2011 10:05:32 -0600 письмо от Steve Borho <[email protected]>: > 2011/2/10 Олег Тазетдинов <[email protected]>: > > That's cool! I would have never found it myself:-) Don't you think it should > be made more prominent? > > Thanks for the answer. > > It's an interesting question. Is this an operation you find yourself > doing often? In all my years of using Mercurial, I think I've done > that once. > > The backout command, which now merges changes to the working parent, > seems to be what you would want to use in most cases. > > -- > Steve Borho ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Tortoisehg-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
