![]() Generally, it’s not a good idea to go and change revision history, which is what folding does. I strongly recommend cloning your Hg repo before undertaking any actions with Mercurial Queues for the first time, if only for peace of mind and the fact that cloning is such an easy operation with Mercurial. revision history), it can have adverse on your Hg repository data can be permanently lost, since the changes that can be made cannot be “backed out” or “reverted”. ![]() Proceed with cautionīecause mq can directly modify changesets (i.e. One such modification is the concept of folding, where one more more changesets are combined to produce a single changeset with the equivalent effect. In this way, previously immutable changesets can be modified. Basically, mq allows you to import changesets to a patch queue, where they can be manipulated. The Mercurial Queues extension ( mq) is one of the most useful Hg extensions available, as it allows for much more than folding. But what about the times when you would like to combine two or more changesets/revisions into a single one that has the combined/overall changes of all of them? In that case, the Mercurial Queues extension provides for the concept of folding, which accomplishes just that. ![]() Most of you using Mercurial/Hg (or revision control in general) will be familiar with the concept of merging, where the changes in a source branch are merged into a target branch, creating a new revision or changeset on the target branch. I haven’t had the opportunity to deal with Git for any period of time, so I can’t comment on the various “ Why X is better than Y” arguments out there. Mercurial is my distributed revision control system of choice, a trait I picked up at my previous job.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |