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