Mercurial > hg > mercurial-crew-with-dirclash
comparison doc/hg.1.txt @ 509:98a2935c3d6c
[PATCH] replace history with log
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[PATCH] replace history with log
From: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
Merge hg history into hg log leaving the first as an alias
(tweaked by mpm: update docs, tests, use existing alias mechanism)
manifest hash: f85001a4373b8b823a6221ba5c506628059d6779
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCwSr1ywK+sNU5EO8RAmbAAJ9HlFkf8/qLOAQUtj8CWxGRPEyzVgCgtXwP
SdnAg1a2q4693+TBiOjrimY=
=w9rf
-----END PGP SIGNATURE-----
author | mpm@selenic.com |
---|---|
date | Tue, 28 Jun 2005 02:48:21 -0800 |
parents | dc1f735dfaac |
children | 003df62ae39f |
comparison
equal
deleted
inserted
replaced
508:42a660abaf75 | 509:98a2935c3d6c |
---|---|
144 | 144 |
145 Repository "heads" are changesets that don't have children | 145 Repository "heads" are changesets that don't have children |
146 changesets. They are where development generally takes place and | 146 changesets. They are where development generally takes place and |
147 are the usual targets for update and merge operations. | 147 are the usual targets for update and merge operations. |
148 | 148 |
149 history:: | 149 identify:: |
150 Print a log of the revision history of the repository. | 150 Print a short summary of the current state of the repo. |
151 | 151 |
152 This summary identifies the repository state using one or two parent | |
153 hash identifiers, followed by a "+" if there are uncommitted changes | |
154 in the working directory, followed by a list of tags for this revision. | |
155 | |
156 aliases: id | |
157 | |
158 import [-p <n> -b <base> -q] <patches>:: | |
159 Import a list of patches and commit them individually. | |
160 | |
161 options: | |
162 -p, --strip <n> directory strip option for patch. This has the same | |
163 meaning as the correnponding patch option | |
164 -b <path> base directory to read patches from | |
165 | |
166 aliases: patch | |
167 | |
168 init:: | |
169 Initialize a new repository in the current directory. | |
170 | |
171 log [file]:: | |
172 Print the revision history of the specified file or the entire project. | |
173 | |
152 By default this command outputs: changeset id and hash, tags, | 174 By default this command outputs: changeset id and hash, tags, |
153 parents, user, date and time, and a summary for each commit. The | 175 parents, user, date and time, and a summary for each commit. The |
154 -v switch adds some more detail, such as changed files, manifest | 176 -v switch adds some more detail, such as changed files, manifest |
155 hashes or message signatures. | 177 hashes or message signatures. |
156 | 178 |
157 To display the history of a given file, see the log command. | 179 aliases: history |
158 | |
159 identify:: | |
160 Print a short summary of the current state of the repo. | |
161 | |
162 This summary identifies the repository state using one or two parent | |
163 hash identifiers, followed by a "+" if there are uncommitted changes | |
164 in the working directory, followed by a list of tags for this revision. | |
165 | |
166 aliases: id | |
167 | |
168 import [-p <n> -b <base> -q] <patches>:: | |
169 Import a list of patches and commit them individually. | |
170 | |
171 options: | |
172 -p, --strip <n> directory strip option for patch. This has the same | |
173 meaning as the correnponding patch option | |
174 -b <path> base directory to read patches from | |
175 | |
176 aliases: patch | |
177 | |
178 init:: | |
179 Initialize a new repository in the current directory. | |
180 | |
181 log <file>:: | |
182 Print the revision history of the specified file. | |
183 | |
184 To display the revision history for the whole repository, use the history | |
185 command. | |
186 | 180 |
187 manifest [revision]:: | 181 manifest [revision]:: |
188 Print a list of version controlled files for the given revision. | 182 Print a list of version controlled files for the given revision. |
189 | 183 |
190 The manifest is the list of files being version controlled. If no revision | 184 The manifest is the list of files being version controlled. If no revision |