Differences between revisions 6 and 8 (spanning 2 versions)
Revision 6 as of 2008-01-05 14:19:54
Size: 631
Editor: abuehl
Comment:
Revision 8 as of 2008-06-06 18:27:21
Size: 1016
Comment: added a note about -1 revision and nullid
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
It is a strictly local ''convenience identifier'' for a file. It can be useful as it is shorter to type than the 40-digit hexadecimal string that uniquely identifies a ["Revision"]. It is a strictly local ''convenience identifier'' for a [:Revision:revision]. It can be useful as it is shorter to type than the 40-digit hexadecimal string that uniquely identifies a revision.
Line 9: Line 9:
Although all files have revision numbers, revision numbers are almost always used to identify ["ChangeSet"]s. Although all files have revision numbers, revision numbers are almost always used to identify a [:ChangeSet:changeset] within a given [:Repository:repository].
Line 13: Line 13:
Revision numbers are ''very likely'' to be different (i.e. to identify a different changeset) in another copy of a ["Repository"]. ''Do not use them'' to talk about changesets with other people. Revision numbers referring to changesets are ''very likely'' to be different in another copy of a repository. ''Do not use them'' to talk about changesets with other people. Use the [:ChangeSetID:changeset ID] instead.

=== Notes ===
An empty repository (with no changesets) has a revision number -1, which corresponds to the '''nullid''' [:Nodeid:nodeid].
For example:
{{{
$ hg log
$ hg status
$ hg head
changeset: -1:000000000000
tag: tip
user:
date: Thu Jan 01 00:00:00 1970 +0000
}}}

Revision number

A revision number is a small integer.

It is a strictly local convenience identifier for a [:Revision:revision]. It can be useful as it is shorter to type than the 40-digit hexadecimal string that uniquely identifies a revision.

Common usage

Although all files have revision numbers, revision numbers are almost always used to identify a [:ChangeSet:changeset] within a given [:Repository:repository].

Pitfalls

Revision numbers referring to changesets are very likely to be different in another copy of a repository. Do not use them to talk about changesets with other people. Use the [:ChangeSetID:changeset ID] instead.

Notes

An empty repository (with no changesets) has a revision number -1, which corresponds to the nullid [:Nodeid:nodeid]. For example:

$ hg log
$ hg status
$ hg head
changeset:   -1:000000000000
tag:         tip
user:
date:        Thu Jan 01 00:00:00 1970 +0000


CategoryGlossary

RevisionNumber (last edited 2013-08-30 06:13:09 by rcl)