Updating yum repositories
Mercurial has a consistent and straightforward approach to dealing with the options that you can pass to commands.It follows the conventions for options that are common to modern Linux and Unix systems.If you need to discuss a changeset with someone, or make a record of a changeset for some other reason (for example, in a bug report), use the hexadecimal identifier.is useful if you already know what you're looking for, you may need to see a complete description of the change, or a list of the files changed, if you're trying to decide whether a changeset is the one you're looking for.
This lets you work on multiple tasks in parallel, each isolated from the others until it's complete and you're ready to integrate it back.
Most commands that print output of some kind will print more output when passed a Now that we have a grasp of viewing history in Mercurial, let's take a look at making some changes and examining them.
The first thing we'll do is isolate our experiment in a repository of its own.
Another is that it remembers where we cloned from, which we'll find useful soon when we want to fetch new changes from another repository.
If our clone succeeded, we should now have a local directory called These files have the same contents and history in our repository as they do in the repository we cloned.