Oct 25, hg clone mercurial-repo real URL is hg/ cd project/ $ hg init # A basic tutorial. Feb 24, Joel Spolsky has put together an extensive Mercurial tutorial with lots of examples and a humorous approach. “Finally, if you haven’t collapsed. Feb 24, If this is advertising, I want more of it. As an SVN curmudgeon, the first part of this tutorial finally persuaded me that I really, really need to give.

Author: Tautaur Malanris
Country: Philippines
Language: English (Spanish)
Genre: Finance
Published (Last): 16 May 2017
Pages: 338
PDF File Size: 10.13 Mb
ePub File Size: 4.91 Mb
ISBN: 432-4-90140-217-1
Downloads: 19898
Price: Free* [*Free Regsitration Required]
Uploader: Vumi

The reluctance to accept it is a bit perplexing to me. A lot will transfer over; some won’t. You can mark these files as ignored in some different ways too. It knows how to diff one file vs.

For example, when merging, a GUI makes things a little bit easier – click a portion of the code, ijit this section”. Compare it to the normal dry, unreadable technical writing on similar subjects and it’s just night and day. I wonder what the meaning of this is.

I’m reusing things I know like pointing: Hard work should be unnecessary.

Hg Init: a Mercurial tutorial by Joel Spolsky | Hacker News

Not to mention their reaction when they see the SHA hashes: Not everybody has time or even interest in learning a new SCM. Everyone will notice pretty quickly if the history gets messed up. The above comment may seem negative but that’s not the intention. I tried Hg first and failed. Your previous commit message will be in the message history drop-down, so you do not have to type it in again from scratch. InclinedPlane on Feb 25, You can traverse the directories to find specific changes and commit them from Explorer.


The merging is smarter, because it has to be, and the history is more complete, because it has to be to enable the merging. Git is too powerful and is overkill for projects in corporate environment and not to mention lack of git plugins for various IDEs that people use.

It happens all the time and you never notice it. Ah, so it’s by Joel.

I wanted to mimic the guide for git at gitinit. I wasn’t intending to argue. During the already almost five years where I’ve been involved in hg, I’ve never seen a single case of problem with truncate. People just need to be trained in how to use it. While this is OK for a very-decentralized project like Linux, it doesn’t work well for projects that have a central repository with hundreds of writers. It’s much easier to spot the differences when comparing text for example, if the diff program uses different background colors and foreground colors, tooltips and other various mercrial hints to help see changes.

Is this still the case? I am not interested in Git advocacy.

Hg Init: a Mercurial tutorial

I have this funny feeling that Joel Spolsky probably does not need to read my blog for advice on effective software marketing. Both were created by kernel hackers for the kernel in April of You do this by making a copy of your repository in a public location that everyone in your group can read. I think the main advantage is really for larger groups.


It is dangerous to manually edit the files in. Hy, you can make “private” branches not actually private with SVN, but they’re still on the server. Once you understand their power, you would wonder why you ever managed to live with Subversion or other centralized VCS. This looks good from an overall why you should learn it point of view and also to help you with the lingo that you should know: Also from experience, the lock-modify-lock is still the right way to do things for some developers and I am saying this with shame.

However, most of those edits are to distinctly different parts of the shared files, and metcurial automatically merged without human intervention, only a tiny handful of merges require manual intervention, a process that takes only a tiny number of people a few minutes to sort out. I get the point that it helps the story to make up a whole life story for each member of the hypothetical development team.

The people I am referring to are not ‘software developers’.