@@ -72,8 +72,7 @@ Command line program to perform common operations (in the context of packaging/d
72
72
Alternatively the location of a remote repository can be given. The
73
73
location should be prefixed by the type of the repository (with a ""+"" in
74
74
between) unless the location ends in "".git"" in which case the prefix is
75
- optional.
76
- "
75
+ optional."
77
76
"``--rev ``, ``--revision=REVISION ``","Select a revision to operate on. Accepts any string that's supported by the
78
77
VCS system that manages the repository, which means you can provide branch
79
78
names, tag names, exact revision ids, etc. This option is used in
@@ -82,55 +81,46 @@ Command line program to perform common operations (in the context of packaging/d
82
81
83
82
If this option is not provided a default revision is selected: ""last:1"" for
84
83
Bazaar repositories, ""master"" for git repositories and ""default"" (not
85
- ""tip""!) for Mercurial repositories.
86
- "
84
+ ""tip""!) for Mercurial repositories."
87
85
``--release=RELEASE_ID ``,"Select a release to operate on. This option works in the same way as the
88
86
``--revision `` option. Please refer to the vcs-repo-mgr documentation for
89
87
details on ""releases"".
90
88
91
89
Although release identifiers are based on branch or tag names they
92
90
may not correspond literally, this is why the release identifier you
93
91
specify here is translated to a global revision id before being passed to
94
- the VCS system.
95
- "
92
+ the VCS system."
96
93
"``-n ``, ``--find-revision-number ``","Print the local revision number (an integer) of the revision given with the
97
94
``--revision `` option. Revision numbers are useful as a build number or when a
98
95
simple, incrementing version number is required. Revision numbers should
99
96
not be used to unambiguously refer to a revision (use revision ids for that
100
97
instead). This option is used in combination with the ``--repository `` and
101
- ``--revision `` options.
102
- "
98
+ ``--revision `` options."
103
99
"``-i ``, ``--find-revision-id ``","Print the global revision id (a string) of the revision given with the
104
100
``--revision `` option. Global revision ids are useful to unambiguously refer to
105
101
a revision. This option is used in combination with the ``--repository `` and
106
- ``--revision `` options.
107
- "
102
+ ``--revision `` options."
108
103
``--list-releases ``,"Print the identifiers of the releases in the repository given with the
109
104
``--repository `` option. The release identifiers are printed on standard
110
- output (one per line), ordered using natural order comparison.
111
- "
105
+ output (one per line), ordered using natural order comparison."
112
106
``--select-release=RELEASE_ID ``,"Print the identifier of the newest release that is not newer than
113
107
``RELEASE_ID `` in the repository given with the ``--repository `` option.
114
- The release identifier is printed on standard output.
115
- "
108
+ The release identifier is printed on standard output."
116
109
"``-s ``, ``--sum-revisions ``","Print the summed revision numbers of multiple repository/revision pairs.
117
110
The repository/revision pairs are taken from the positional arguments to
118
111
vcs-repo-mgr.
119
112
120
113
This is useful when you're building a package based on revisions from
121
114
multiple VCS repositories. By taking changes in all repositories into
122
115
account when generating version numbers you can make sure that your version
123
- number is bumped with every single change.
124
- "
116
+ number is bumped with every single change."
125
117
``--vcs-control-field ``,"Print a line containing a Debian control file field and value. The field
126
118
name will be one of ""Vcs-Bzr"", ""Vcs-Hg"" or ""Vcs-Git"". The value will be the
127
119
repository's remote location and the selected revision (separated by a ""#""
128
- character).
129
- "
120
+ character)."
130
121
"``-u ``, ``--update ``","Create/update the local clone of a remote repository by pulling the latest
131
122
changes from the remote repository. This option is used in combination with
132
- the ``--repository `` option.
133
- "
123
+ the ``--repository `` option."
134
124
"``-m ``, ``--merge-up ``","Merge a change into one or more release branches and the default branch.
135
125
136
126
By default merging starts from the current branch. You can explicitly
@@ -144,17 +134,14 @@ Command line program to perform common operations (in the context of packaging/d
144
134
145
135
If the feature branch is located in a different repository you can prefix
146
136
the location of the repository to the name of the feature branch with a ""#""
147
- token in between, to delimit the location from the branch name.
148
- "
137
+ token in between, to delimit the location from the branch name."
149
138
"``-e ``, ``--export=DIRECTORY ``","Export the contents of a specific revision of a repository to a local
150
139
directory. This option is used in combination with the ``--repository `` and
151
- ``--revision `` options.
152
- "
140
+ ``--revision `` options."
153
141
"``-d ``, ``--find-directory ``","Print the absolute pathname of a local repository. This option is used in
154
- combination with the ``--repository `` option.
155
- "
156
- "``-v ``, ``--verbose ``","Make more noise.
157
- "
142
+ combination with the ``--repository `` option."
143
+ "``-v ``, ``--verbose ``",Increase logging verbosity (can be repeated).
144
+ "``-q ``, ``--quiet ``",Decrease logging verbosity (can be repeated).
158
145
"``-h ``, ``--help ``","Show this message and exit.
159
146
"
160
147
0 commit comments