Changes

#: 1- The .hg directory is the “real” repository, and all of the files and directories that coexist with it are said to live in the ''working directory''. ::An easy way to remember the distinction is that the ''repository'' contains the history of your project, while the ''working directory'' contains a snapshot of your project at a particular point in history.#: 2- The ''hg log'' command gives us a view of the history of changes in the repository. By default, this command prints a brief paragraph of output for each change to the project that was recorded. :: Each of these recorded events are called a ''changeset'', because it can contain a record of changes to several files. ''Changeset'' is also referred to as''change'', ''cset'', ''revision'' or ''rev''.#: 3- ''Changeset'' field has the format of a number (''identifier'', which is only valid in that repository) followed by a colon, followed by a hexadecimal (or hex) string. These are identifiers for the changeset. ::The hex string is a unique identifier: the same hex string will always refer to the same changeset in every copy of this repository. The number is shorter and easier to type than the hex string, but it isn't unique: the same number in two different clones of a repository may identify different changesets. ''changeset: 0:0a04b987be5a''#:4- Mercurial uses revision numbers purely as a convenient shorthand. 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.#:5- Some changesets, have a tag field. A ''tag'' is another way to identify a changeset, by giving it an easy-to-remember name. ''tag: tip''#:6- To get the changeset id of the tipmost changeset of a remote repository you can do: When it changes, you have new changesets in the remote repository.[http://mercurial.selenic.com/wiki/FAQ#FAQ.2BAC8-CommonProblems.How_can_I_find_out_if_there_are_new_changesets_in_a_remote_repository.3F]