Mercurial > public > mercurial-scm > hg
annotate mercurial/help/glossary.txt @ 18426:01638b51df44
hgweb: ignore filtered revision in revnav
This changeset checks that a revision is known before adding it to the
navigation.
This will prevent traceback on filtered repository. This changeset result in an
incorrect behaviors, Navigation link may be dropped without any replacement.
However this bad navigation generation is much better than a crash
| author | Pierre-Yves David <pierre-yves.david@logilab.fr> |
|---|---|
| date | Wed, 16 Jan 2013 14:19:28 +0100 |
| parents | 8298d220cbf9 |
| children | 7547bcc1a3ad |
| rev | line source |
|---|---|
| 11356 | 1 Ancestor |
| 2 Any changeset that can be reached by an unbroken chain of parent | |
| 3 changesets from a given changeset. More precisely, the ancestors | |
| 4 of a changeset can be defined by two properties: a parent of a | |
| 5 changeset is an ancestor, and a parent of an ancestor is an | |
| 6 ancestor. See also: 'Descendant'. | |
| 7 | |
|
14630
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
8 Bookmark |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
9 Bookmarks are pointers to certain commits that move when |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
10 committing. They are similar to tags in that it is possible to use |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
11 bookmark names in all places where Mercurial expects a changeset |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
12 ID, e.g., with :hg:`update`. Unlike tags, bookmarks move along |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
13 when you make a commit. |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
14 |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
15 Bookmarks can be renamed, copied and deleted. Bookmarks are local, |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
16 unless they are explicitly pushed or pulled between repositories. |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
17 Pushing and pulling bookmarks allow you to collaborate with others |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
18 on a branch without creating a named branch. |
|
f536151d392f
glossary: add entry for "Bookmark"
Martin Geisler <mg@aragost.com>
parents:
14629
diff
changeset
|
19 |
| 11356 | 20 Branch |
| 21 (Noun) A child changeset that has been created from a parent that | |
| 22 is not a head. These are known as topological branches, see | |
|
11437
9fa255c32406
help: glossary.txt formatting fixes
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11436
diff
changeset
|
23 'Branch, topological'. If a topological branch is named, it becomes |
| 11356 | 24 a named branch. If a topological branch is not named, it becomes |
| 25 an anonymous branch. See 'Branch, anonymous' and 'Branch, named'. | |
| 26 | |
| 27 Branches may be created when changes are pulled from or pushed to | |
| 28 a remote repository, since new heads may be created by these | |
| 29 operations. Note that the term branch can also be used informally | |
| 30 to describe a development process in which certain development is | |
| 11685 | 31 done independently of other development. This is sometimes done |
| 11356 | 32 explicitly with a named branch, but it can also be done locally, |
| 33 using bookmarks or clones and anonymous branches. | |
| 34 | |
| 35 Example: "The experimental branch". | |
| 36 | |
| 37 (Verb) The action of creating a child changeset which results in | |
| 38 its parent having more than one child. | |
| 39 | |
| 40 Example: "I'm going to branch at X". | |
| 41 | |
| 42 Branch, anonymous | |
| 43 Every time a new child changeset is created from a parent that is not | |
| 44 a head and the name of the branch is not changed, a new anonymous | |
| 45 branch is created. | |
| 46 | |
| 47 Branch, closed | |
| 48 A named branch whose branch heads have all been closed. | |
| 49 | |
| 50 Branch, default | |
| 51 The branch assigned to a changeset when no name has previously been | |
| 52 assigned. | |
| 53 | |
| 54 Branch head | |
| 55 See 'Head, branch'. | |
| 56 | |
|
11911
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
57 Branch, inactive |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
58 If a named branch has no topological heads, it is considered to be |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
59 inactive. As an example, a feature branch becomes inactive when it |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
60 is merged into the default branch. The :hg:`branches` command |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
61 shows inactive branches by default, though they can be hidden with |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
62 :hg:`branches --active`. |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
63 |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
64 NOTE: this concept is deprecated because it is too implicit. |
| 11927 | 65 Branches should now be explicitly closed using :hg:`commit |
|
11911
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
66 --close-branch` when they are no longer needed. |
|
528ff7610cba
glossary: add entry for "Branch, inactive"
Martin Geisler <mg@lazybytes.net>
parents:
11511
diff
changeset
|
67 |
| 11356 | 68 Branch, named |
| 69 A collection of changesets which have the same branch name. By | |
| 70 default, children of a changeset in a named branch belong to the | |
| 71 same named branch. A child can be explicitly assigned to a | |
| 72 different branch. See :hg:`help branch`, :hg:`help branches` and | |
| 73 :hg:`commit --close-branch` for more information on managing | |
| 74 branches. | |
| 75 | |
| 76 Named branches can be thought of as a kind of namespace, dividing | |
| 77 the collection of changesets that comprise the repository into a | |
| 78 collection of disjoint subsets. A named branch is not necessarily | |
| 79 a topological branch. If a new named branch is created from the | |
| 80 head of another named branch, or the default branch, but no | |
|
11436
45eadf71df22
help: fix glossary.txt named branches description
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11356
diff
changeset
|
81 further changesets are added to that previous branch, then that |
|
45eadf71df22
help: fix glossary.txt named branches description
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11356
diff
changeset
|
82 previous branch will be a branch in name only. |
| 11356 | 83 |
| 84 Branch tip | |
| 85 See 'Tip, branch'. | |
| 86 | |
| 87 Branch, topological | |
| 88 Every time a new child changeset is created from a parent that is | |
| 89 not a head, a new topological branch is created. If a topological | |
| 90 branch is named, it becomes a named branch. If a topological | |
| 91 branch is not named, it becomes an anonymous branch of the | |
| 92 current, possibly default, branch. | |
| 93 | |
| 94 Changelog | |
| 95 A record of the changesets in the order in which they were added | |
| 96 to the repository. This includes details such as changeset id, | |
| 97 author, commit message, date, and list of changed files. | |
| 98 | |
| 99 Changeset | |
| 100 A snapshot of the state of the repository used to record a change. | |
| 101 | |
| 102 Changeset, child | |
| 103 The converse of parent changeset: if P is a parent of C, then C is | |
| 104 a child of P. There is no limit to the number of children that a | |
| 105 changeset may have. | |
| 106 | |
| 107 Changeset id | |
| 108 A SHA-1 hash that uniquely identifies a changeset. It may be | |
|
11718
3e979f47a4c9
help: fix bytes/digit confusion for hashes
Matt Mackall <mpm@selenic.com>
parents:
11685
diff
changeset
|
109 represented as either a "long" 40 hexadecimal digit string, or a |
|
3e979f47a4c9
help: fix bytes/digit confusion for hashes
Matt Mackall <mpm@selenic.com>
parents:
11685
diff
changeset
|
110 "short" 12 hexadecimal digit string. |
| 11356 | 111 |
| 112 Changeset, merge | |
| 113 A changeset with two parents. This occurs when a merge is | |
| 114 committed. | |
| 115 | |
| 116 Changeset, parent | |
| 117 A revision upon which a child changeset is based. Specifically, a | |
| 118 parent changeset of a changeset C is a changeset whose node | |
| 119 immediately precedes C in the DAG. Changesets have at most two | |
| 120 parents. | |
| 121 | |
| 122 Checkout | |
| 123 (Noun) The working directory being updated to a specific | |
| 124 revision. This use should probably be avoided where possible, as | |
| 125 changeset is much more appropriate than checkout in this context. | |
| 126 | |
| 127 Example: "I'm using checkout X." | |
| 128 | |
| 129 (Verb) Updating the working directory to a specific changeset. See | |
| 130 :hg:`help update`. | |
| 131 | |
| 132 Example: "I'm going to check out changeset X." | |
| 133 | |
| 134 Child changeset | |
| 135 See 'Changeset, child'. | |
| 136 | |
| 137 Close changeset | |
|
16501
340d047ea577
doc: fix careless document miss for term 'Close changeset' in glossary
FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
parents:
16039
diff
changeset
|
138 See 'Head, closed branch' |
| 11356 | 139 |
| 140 Closed branch | |
| 141 See 'Branch, closed'. | |
| 142 | |
| 143 Clone | |
| 144 (Noun) An entire or partial copy of a repository. The partial | |
| 145 clone must be in the form of a revision and its ancestors. | |
| 146 | |
| 147 Example: "Is your clone up to date?". | |
| 148 | |
| 149 (Verb) The process of creating a clone, using :hg:`clone`. | |
| 150 | |
| 151 Example: "I'm going to clone the repository". | |
| 152 | |
| 153 Closed branch head | |
| 154 See 'Head, closed branch'. | |
| 155 | |
| 156 Commit | |
| 157 (Noun) A synonym for changeset. | |
| 158 | |
| 159 Example: "Is the bug fixed in your recent commit?" | |
| 160 | |
| 161 (Verb) The act of recording changes to a repository. When files | |
| 162 are committed in a working directory, Mercurial finds the | |
| 163 differences between the committed files and their parent | |
| 164 changeset, creating a new changeset in the repository. | |
| 165 | |
| 166 Example: "You should commit those changes now." | |
| 167 | |
| 168 Cset | |
| 169 A common abbreviation of the term changeset. | |
| 170 | |
| 171 DAG | |
| 172 The repository of changesets of a distributed version control | |
| 173 system (DVCS) can be described as a directed acyclic graph (DAG), | |
| 174 consisting of nodes and edges, where nodes correspond to | |
| 175 changesets and edges imply a parent -> child relation. This graph | |
| 176 can be visualized by graphical tools such as :hg:`glog` | |
|
11437
9fa255c32406
help: glossary.txt formatting fixes
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11436
diff
changeset
|
177 (graphlog). In Mercurial, the DAG is limited by the requirement |
| 11356 | 178 for children to have at most two parents. |
| 179 | |
| 180 Default branch | |
| 181 See 'Branch, default'. | |
| 182 | |
| 183 Descendant | |
| 184 Any changeset that can be reached by a chain of child changesets | |
| 185 from a given changeset. More precisely, the descendants of a | |
| 186 changeset can be defined by two properties: the child of a | |
| 187 changeset is a descendant, and the child of a descendant is a | |
| 188 descendant. See also: 'Ancestor'. | |
| 189 | |
| 190 Diff | |
| 191 (Noun) The difference between the contents and attributes of files | |
| 192 in two changesets or a changeset and the current working | |
| 193 directory. The difference is usually represented in a standard | |
| 194 form called a "diff" or "patch". The "git diff" format is used | |
| 195 when the changes include copies, renames, or changes to file | |
| 196 attributes, none of which can be represented/handled by classic | |
| 197 "diff" and "patch". | |
| 198 | |
| 199 Example: "Did you see my correction in the diff?" | |
| 200 | |
| 201 (Verb) Diffing two changesets is the action of creating a diff or | |
| 202 patch. | |
| 203 | |
| 204 Example: "If you diff with changeset X, you will see what I mean." | |
| 205 | |
| 206 Directory, working | |
| 207 The working directory represents the state of the files tracked by | |
| 208 Mercurial, that will be recorded in the next commit. The working | |
| 209 directory initially corresponds to the snapshot at an existing | |
| 210 changeset, known as the parent of the working directory. See | |
|
11511
9d905b9769af
glossary: fixed typo in "Directory, working" description
Renato Cunha <renatoc@gmail.com>
parents:
11437
diff
changeset
|
211 'Parent, working directory'. The state may be modified by changes |
| 11356 | 212 to the files introduced manually or by a merge. The repository |
| 213 metadata exists in the .hg directory inside the working directory. | |
| 214 | |
| 16037 | 215 Draft |
| 216 Changesets in the draft phase have not been shared with publishing | |
| 217 repositories and may thus be safely changed by history-modifying | |
| 218 extensions. See :hg:`help phases`. | |
| 219 | |
| 11356 | 220 Graph |
| 221 See DAG and :hg:`help graphlog`. | |
| 222 | |
| 223 Head | |
| 224 The term 'head' may be used to refer to both a branch head or a | |
| 225 repository head, depending on the context. See 'Head, branch' and | |
| 226 'Head, repository' for specific definitions. | |
| 227 | |
| 228 Heads are where development generally takes place and are the | |
| 229 usual targets for update and merge operations. | |
| 230 | |
| 231 Head, branch | |
| 232 A changeset with no descendants on the same named branch. | |
| 233 | |
| 234 Head, closed branch | |
| 235 A changeset that marks a head as no longer interesting. The closed | |
| 236 head is no longer listed by :hg:`heads`. A branch is considered | |
| 237 closed when all its heads are closed and consequently is not | |
| 238 listed by :hg:`branches`. | |
| 239 | |
|
16502
8298d220cbf9
doc: add description about re-opening closed heads to 'Head, closed branch' in glossary
FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
parents:
16501
diff
changeset
|
240 Closed heads can be re-opened by committing new changeset as the |
|
8298d220cbf9
doc: add description about re-opening closed heads to 'Head, closed branch' in glossary
FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
parents:
16501
diff
changeset
|
241 child of the changeset that marks a head as closed. |
|
8298d220cbf9
doc: add description about re-opening closed heads to 'Head, closed branch' in glossary
FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
parents:
16501
diff
changeset
|
242 |
| 11356 | 243 Head, repository |
| 244 A topological head which has not been closed. | |
| 245 | |
| 246 Head, topological | |
| 247 A changeset with no children in the repository. | |
| 248 | |
| 249 History, immutable | |
| 250 Once committed, changesets cannot be altered. Extensions which | |
| 251 appear to change history actually create new changesets that | |
| 252 replace existing ones, and then destroy the old changesets. Doing | |
| 253 so in public repositories can result in old changesets being | |
| 254 reintroduced to the repository. | |
| 255 | |
| 256 History, rewriting | |
| 257 The changesets in a repository are immutable. However, extensions | |
| 258 to Mercurial can be used to alter the repository, usually in such | |
| 259 a way as to preserve changeset contents. | |
| 260 | |
| 261 Immutable history | |
| 262 See 'History, immutable'. | |
| 263 | |
| 264 Merge changeset | |
| 265 See 'Changeset, merge'. | |
| 266 | |
| 267 Manifest | |
| 268 Each changeset has a manifest, which is the list of files that are | |
| 269 tracked by the changeset. | |
| 270 | |
| 271 Merge | |
| 272 Used to bring together divergent branches of work. When you update | |
| 273 to a changeset and then merge another changeset, you bring the | |
| 274 history of the latter changeset into your working directory. Once | |
| 275 conflicts are resolved (and marked), this merge may be committed | |
| 276 as a merge changeset, bringing two branches together in the DAG. | |
| 277 | |
| 278 Named branch | |
| 279 See 'Branch, named'. | |
| 280 | |
| 281 Null changeset | |
| 282 The empty changeset. It is the parent state of newly-initialized | |
| 283 repositories and repositories with no checked out revision. It is | |
| 284 thus the parent of root changesets and the effective ancestor when | |
| 285 merging unrelated changesets. Can be specified by the alias 'null' | |
| 286 or by the changeset ID '000000000000'. | |
| 287 | |
| 288 Parent | |
| 289 See 'Changeset, parent'. | |
| 290 | |
| 291 Parent changeset | |
| 292 See 'Changeset, parent'. | |
| 293 | |
| 294 Parent, working directory | |
| 295 The working directory parent reflects a virtual revision which is | |
| 296 the child of the changeset (or two changesets with an uncommitted | |
| 297 merge) shown by :hg:`parents`. This is changed with | |
| 298 :hg:`update`. Other commands to see the working directory parent | |
| 299 are :hg:`summary` and :hg:`id`. Can be specified by the alias ".". | |
| 300 | |
| 301 Patch | |
| 302 (Noun) The product of a diff operation. | |
| 303 | |
| 304 Example: "I've sent you my patch." | |
| 305 | |
| 306 (Verb) The process of using a patch file to transform one | |
| 307 changeset into another. | |
| 308 | |
| 309 Example: "You will need to patch that revision." | |
| 310 | |
| 16037 | 311 Phase |
| 312 A per-changeset state tracking how the changeset has been or | |
| 313 should be shared. See :hg:`help phases`. | |
| 314 | |
| 315 Public | |
| 316 Changesets in the public phase have been shared with publishing | |
| 317 repositories and are therefore considered immutable. See :hg:`help | |
| 318 phases`. | |
| 319 | |
| 11356 | 320 Pull |
| 321 An operation in which changesets in a remote repository which are | |
| 322 not in the local repository are brought into the local | |
| 323 repository. Note that this operation without special arguments | |
| 324 only updates the repository, it does not update the files in the | |
| 325 working directory. See :hg:`help pull`. | |
| 326 | |
| 327 Push | |
| 328 An operation in which changesets in a local repository which are | |
| 329 not in a remote repository are sent to the remote repository. Note | |
| 330 that this operation only adds changesets which have been committed | |
| 331 locally to the remote repository. Uncommitted changes are not | |
| 332 sent. See :hg:`help push`. | |
| 333 | |
| 334 Repository | |
| 335 The metadata describing all recorded states of a collection of | |
| 336 files. Each recorded state is represented by a changeset. A | |
| 337 repository is usually (but not always) found in the ``.hg`` | |
| 338 subdirectory of a working directory. Any recorded state can be | |
| 339 recreated by "updating" a working directory to a specific | |
| 340 changeset. | |
| 341 | |
| 342 Repository head | |
| 343 See 'Head, repository'. | |
| 344 | |
| 345 Revision | |
| 346 A state of the repository at some point in time. Earlier revisions | |
| 347 can be updated to by using :hg:`update`. See also 'Revision | |
| 348 number'; See also 'Changeset'. | |
| 349 | |
| 350 Revision number | |
| 351 This integer uniquely identifies a changeset in a specific | |
| 352 repository. It represents the order in which changesets were added | |
| 353 to a repository, starting with revision number 0. Note that the | |
| 354 revision number may be different in each clone of a repository. To | |
| 355 identify changesets uniquely between different clones, see | |
| 356 'Changeset id'. | |
| 357 | |
| 358 Revlog | |
| 359 History storage mechanism used by Mercurial. It is a form of delta | |
| 360 encoding, with occasional full revision of data followed by delta | |
| 361 of each successive revision. It includes data and an index | |
| 362 pointing to the data. | |
| 363 | |
| 364 Rewriting history | |
|
11437
9fa255c32406
help: glossary.txt formatting fixes
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11436
diff
changeset
|
365 See 'History, rewriting'. |
| 11356 | 366 |
| 367 Root | |
| 368 A changeset that has only the null changeset as its parent. Most | |
| 369 repositories have only a single root changeset. | |
| 370 | |
| 16037 | 371 Secret |
|
16039
093b75c7b44b
pull: return 1 when no changes found (BC)
Matt Mackall <mpm@selenic.com>
parents:
16037
diff
changeset
|
372 Changesets in the secret phase may not be shared via push, pull, |
|
093b75c7b44b
pull: return 1 when no changes found (BC)
Matt Mackall <mpm@selenic.com>
parents:
16037
diff
changeset
|
373 or clone. See :hg:`help phases`. |
| 16037 | 374 |
|
14629
c3f2152e423d
glossary: add entry for "Tag"
Martin Geisler <mg@aragost.com>
parents:
11937
diff
changeset
|
375 Tag |
|
c3f2152e423d
glossary: add entry for "Tag"
Martin Geisler <mg@aragost.com>
parents:
11937
diff
changeset
|
376 An alternative name given to a changeset. Tags can be used in all |
|
c3f2152e423d
glossary: add entry for "Tag"
Martin Geisler <mg@aragost.com>
parents:
11937
diff
changeset
|
377 places where Mercurial expects a changeset ID, e.g., with |
|
c3f2152e423d
glossary: add entry for "Tag"
Martin Geisler <mg@aragost.com>
parents:
11937
diff
changeset
|
378 :hg:`update`. The creation of a tag is stored in the history and |
|
c3f2152e423d
glossary: add entry for "Tag"
Martin Geisler <mg@aragost.com>
parents:
11937
diff
changeset
|
379 will thus automatically be shared with other using push and pull. |
|
c3f2152e423d
glossary: add entry for "Tag"
Martin Geisler <mg@aragost.com>
parents:
11937
diff
changeset
|
380 |
| 11356 | 381 Tip |
| 382 The changeset with the highest revision number. It is the changeset | |
| 383 most recently added in a repository. | |
| 384 | |
| 385 Tip, branch | |
| 386 The head of a given branch with the highest revision number. When | |
| 387 a branch name is used as a revision identifier, it refers to the | |
| 388 branch tip. See also 'Branch, head'. Note that because revision | |
| 389 numbers may be different in different repository clones, the | |
| 390 branch tip may be different in different cloned repositories. | |
| 391 | |
| 392 Update | |
| 393 (Noun) Another synonym of changeset. | |
| 394 | |
|
11437
9fa255c32406
help: glossary.txt formatting fixes
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11436
diff
changeset
|
395 Example: "I've pushed an update". |
| 11356 | 396 |
| 397 (Verb) This term is usually used to describe updating the state of | |
| 398 the working directory to that of a specific changeset. See | |
| 399 :hg:`help update`. | |
| 400 | |
| 401 Example: "You should update". | |
| 402 | |
| 403 Working directory | |
| 404 See 'Directory, working'. | |
| 405 | |
| 406 Working directory parent | |
|
11437
9fa255c32406
help: glossary.txt formatting fixes
Wagner Bruna <wbruna@softwareexpress.com.br>
parents:
11436
diff
changeset
|
407 See 'Parent, working directory'. |