Show More
@@ -55,6 +55,8 b' Mercurial commands:' | |||||
55 | $ hg remove bar # mark a file as removed |
|
55 | $ hg remove bar # mark a file as removed | |
56 | $ hg verify # check repo integrity |
|
56 | $ hg verify # check repo integrity | |
57 | $ hg tags # show current tags |
|
57 | $ hg tags # show current tags | |
|
58 | $ hg tag <name> # tag current tip with distributed tag <name> | |||
|
59 | $ hg tag -l <name> # tag current tip with local tag <name> | |||
58 | $ hg annotate [files] # show changeset numbers for each file line |
|
60 | $ hg annotate [files] # show changeset numbers for each file line | |
59 |
|
61 | |||
60 | Branching and merging: |
|
62 | Branching and merging: |
@@ -124,10 +124,10 b' a tag. Thus tagging a revision must be d' | |||||
124 |
|
124 | |||
125 | .Q. What if I want to just keep local tags? |
|
125 | .Q. What if I want to just keep local tags? | |
126 |
|
126 | |||
127 | You can add a section called "[tags]" to your .hg/hgrc which contains |
|
127 | You can use "hg tag" command with an option "-l" or "--local". This | |
128 | a list of tag = changeset ID pairs. Unlike traditional tags, these are |
|
128 | will store the tag in the file .hg/localtags, which will not be | |
129 | only visible in the local repository, but otherwise act just like |
|
129 | distributed or versioned. The format of this file is identical to the | |
130 | normal tags. |
|
130 | one of .hgtags and the tags stored there are handled the same. | |
131 |
|
131 | |||
132 |
|
132 | |||
133 | .Q. How do tags work with multiple heads? |
|
133 | .Q. How do tags work with multiple heads? |
@@ -329,7 +329,7 b' status::' | |||||
329 | R = removed |
|
329 | R = removed | |
330 | ? = not tracked |
|
330 | ? = not tracked | |
331 |
|
331 | |||
332 | tag [-t <text> -d <datecode> -u <user>] <name> [revision]:: |
|
332 | tag [-l -t <text> -d <datecode> -u <user>] <name> [revision]:: | |
333 | Name a particular revision using <name>. |
|
333 | Name a particular revision using <name>. | |
334 |
|
334 | |||
335 | Tags are used to name particular revisions of the repository and are |
|
335 | Tags are used to name particular revisions of the repository and are | |
@@ -344,13 +344,14 b' tag [-t <text> -d <datecode> -u <user>] ' | |||||
344 | necessary. |
|
344 | necessary. | |
345 |
|
345 | |||
346 | options: |
|
346 | options: | |
|
347 | -l, --local make the tag local | |||
347 | -t, --text <text> message for tag commit log entry |
|
348 | -t, --text <text> message for tag commit log entry | |
348 | -d, --date <datecode> datecode for commit |
|
349 | -d, --date <datecode> datecode for commit | |
349 | -u, --user <user> user for commit |
|
350 | -u, --user <user> user for commit | |
350 |
|
351 | |||
351 | Note: Mercurial also has support for "local tags" that are not |
|
352 | Note: Local tags are not version-controlled or distributed and are | |
352 | version-controlled or distributed which are stored in the .hg/hgrc |
|
353 | stored in the .hg/localtags file. If there exists a local tag and | |
353 | file. |
|
354 | a public tag with the same name, local tag is used. | |
354 |
|
355 | |||
355 | tags:: |
|
356 | tags:: | |
356 | List the repository tags. |
|
357 | List the repository tags. |
General Comments 0
You need to be logged in to leave comments.
Login now