![]() The MQ extension lets you treat a stack of patches as works-in-progress. The output of a developer (on a good day, anyway) is patches. The mqext extension can make this much easier. Version your patch queue to save changes.Ensure you use the latest stable release of Mercurial.Otherwise you will lose any changes to binary files. It is sharp and can mess up your repository if used incorrectly. If someone pulls one of them, you'll never get rid of it. MQ creates temporary changesets in your repo. Don't use MQ in a repository anyone might pull from.It replaces your previous version of the current patch with what's in your working directory. Watch your step.įor instance, unless you're running the mqext, hg qrefresh is destructive. Certain operations make it easy to lose work. MQ puts you in a position where you're doing fairly complicated stuff to your uncommitted work. All users are therefore strongly encouraged to read the next section before starting to use MQ. Users should note, though, that MQ is a powerful tool, and this can also lead to mistakes. However, MQ remains a feasible patch-management tool for those who are used to older version control systems and don't want to adopt a Git-style workflow. It is strongly recommended that new users adopt a bookmark-based workflow and do not use MQ. See the official Mercurial docs on bookmarks. Note that Mercurial bookmarks are very similar to Git branches. People who are used to Git's branch-based workflow may find MQ hard to adapt to, and should consider using Mercurial bookmarks or branches instead.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |