However, I make no claim that this is the correct (or even a correct) way to use TortoiseHg and Mercurial. This is the way that feels the most natural to me. There are a bewildering number of different ways you can work with Mercurial. Also, this is Windows-centric, but I imagine it will be a similar experience for Linux and Mac OS users as well. Nor do I explain more than a small fraction of the capabilities of and terminology used by version control systems like Mercurial. But I don't walk through installation of the software. This aimed at newbies and I've tried to not assume much prior knowledge. The three sections of this guide ( The Basics, Branching, and Bitbucket) are intended to be read separately or in order. Mercurial is incredibly flexible, so it may take a while to find the method that works best for you!Īn explanation of using named branches in projects with TortoiseHg for Windows and collaborating with others via Bitbucket. You can always branch off of old commits at any time (with a name or not), so pre-creating them like I describe is unnecessary. I've also found that I don't have as much need for branches as described below. But now I'm on a Linux desktop and I use Mercurial at the command line ( hg). I still () love Mercurial and use it every day. I'll leave this page up in the hopes that it will remain useful for others. I firmly believe that Mercurial is a great SCM, but it's hard to imagine going back to it now. I'm afraid this has been the final nail in the coffin for hg for me. UPDATE : Git is now a professional requirement at my workplace and Bitbucket has dropped support for Mercurial. Dave's Visual Guide to TortoiseHg and Mercurial's Named Branches.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |