AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Tortoisehg tag vs bookmark2/19/2023 ![]() ![]() The first thing we need to do is to create the repository - assuming it doesn't exist yet: if that's not the case, just skip this step and go further.ĭon't forget to also issue a first commit in order to add some files to the local repository. Let's see how we can effectively sinchronize a local Mercurial repository on our HDD with a remote Git repository hosted on GitHub without using Git. You just have to learn how to properly do that. Once you have it activated, you can easily access any Git repository - including those created on the GitHub web site: it's as simple as that. Luckily for me, I found a neat native plugin of the Mercurial GUI suite I was using - TortoiseHG, which is also one of the most widely known and used on Windows platforms - who was able to do exactly what I needed: creating an interop bridge between Mercurial commands and any existing Git repository. The plugin name is hggit and it's included in the TortoiseHG default package: it can be activated with a single click via he Extensions panel: Neither we could add a second repository: it would have meant duplicating the burden of the aforementioned clients. Needless to say, changing SCM on-the-fly was not an option - we wouldn't want to lose the history, let alone re-configuring each and every developer client. A huge, widely distribuited, Mercurial-based repository. Personally I never had to answer such a question for a long while - until a customer asked me to put his project repository on GitHub. The first question you could ask is: does it even make any sense? Why would we want to use a Git-related web host if we don't feel like adopting Git? Why don't just use BitBucket instead? Let's bring the main topic back: how to effectively use GitHub site & services with Mercurial instead of Git. Interoperability between Mercurial and Git by using TortoiseHG DVCS Analysis: Git and Mercurial (by Google tech).The first one is practical, technical and analytic, whilst the latter is more theoretical and fun: just pick the one you feel most suited for your style, just like you'll often end up choosing your SCM. If you're looking for a deeper analysis of the similarities and the differences between Git e Mercurial I strongly suggest you to start by reading these two excellent (despite their age) posts. To put it in other words, I don't think I ever missed one of them while working with the other one. I don't want to go further than that, let alone saying which SCM would be better and why: in my personal opinion, being an enthusiast of both Git and Mercurial, I think that they are two amazing products which - despite their slightly different architectural approach - are equally able to perfectly fullfill almost any modern developing scenario. the almost-simultaneos diffusion of Mercurial (formerly HG), another distribuited SCM featuring tools and settings as neat as Git ones, with a generally better support for Windows platforms, software and developer frameworks.Īnother strong reason which favored Mercurial over Git on windows platforms was, in 2008, the launch of the website, entirely based on Mercurial (until 2011, when Git was adopted too) and very similar to GitHub in almost any way.a late win32 porting of the most used UI - msysgit e TortoiseGit among others - which tend to be preferred by most Windows developers who tend to despise a bare c ommand-line interface.Conversely, it's still slightly less popular between Windows users for the following reasons: While Git is widely adopted by either Windows and Linux developer communities, the latter certainly is its true love source - after all it was developed by a certain Linus Torvalds. These - togheter with the GitHub project itself- are the reasons why it gradually crushed the competitors, including some very praised open-source industry standards such as CVS and SVN - which were based on a traditional, less-modern centralized SCM paradigm. If you know what I'm talking about, keep reading: you're most certainly aware that in order to use the GitHub service you need to adopt Git, which is not only the most used source-control manager (SCM from now on) of the current decade, yet also a very brilliant and innovative piece of work due to its distribuited, versatile and elegant approach. Taking a look to the and official site won't hurt either. If I'm wrong and you never head about it I strongly suggest you to fill this huge gap by reading (at least) the GitHub and Git wikipedia pages. ![]() I don't think there's a single developer who doesn't know GitHub, the popular source-control web hosting service for Git. ![]()
0 Comments
Read More
Leave a Reply. |