/usr/share/doc/reposurgeon/repotool.html is in reposurgeon 3.37-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>repotool</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="repotool.1"></a><div class="titlepage"></div><div class="refnamediv"><a name="name"></a><h2>Name</h2><p>repotool — query or manipulate a CVS, Subversion, git, bzr, hg, or
darcs repository in a uniform way</p></div><div class="refsynopsisdiv"><a name="synopsis"></a><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">repotool</code> [<em class="replaceable"><code>action</code></em>] [<em class="replaceable"><code>URL-or-dir</code></em>]</p></div></div><div class="refsect1"><a name="description"></a><h2>DESCRIPTION</h2><p>repotool is a script wrapper around repository operations that
differ by version-control system. It is little use by itself,
existing mainly to generate and simplify a conversion makefile usable
with
<span class="citerefentry"><span class="refentrytitle">reposurgeon</span>(1)</span>.</p><p>Not all actions are supported on all systems. You will get an
error message and a return value of 1 when attempting an unsupported
action.</p><p>The "initialize" option takes a project name (and, optionally,
following source and target VCCS types) and generates a
Makefile that will sequence various steps of a repository
conversion. It also generates stub lift and options files. This is
meant to be run in an empty work directory, and it is an error to do
'initialize' where any of these files already exist. Afterwards, you
will need to set some variables in the Makefile; read its header
comment.</p><p>The 'export' action, run from within a repository directory,
dumps a copy of a CVS, Subversion, git, bzr, hg, or darcs repository
to a flat history file readable by reposurgeon. The format is usually
a git-fast-import stream, except that Subversion repositories export
as Subversion dump files; the point is to be a lossless
erepresentation, or as close to one as possible.</p><p>The 'tags' option, run from within a repository directory,
returns a list of the repository's release tags.</p><p>The 'branches' option, run from within a repository directory ,
returns a list of the repository's branch names.</p><p>The 'checkout' option checks out a working copy of the
repository. It must be called from within the repository. It takes one
required argument - the checkout directory location. It may take a
following optional argument which is a tag or revision specification;
if this argument is not given, the tip (most recent) mainline revision
is assumed.</p><p>The 'compare' action takes two repository directories and a
revision spec (typically a tag name). If the revision spec is omitted,
the tip of the main line of both repositories will be used. The
selected revisions are cpmpared with diff -q -r, with noise due to
SCCS/RCS/CVS keyword expansion ignored. You can follow the command
verb with one or more -x options followed by basenames of paths to
exclude from comparison. You can get a context-diff report on file
differences with the -u option.</p><p>The 'compare-tags' action takes two repository directories,
extracts a list of tags from the first, then compares the repository
contents at each tag in the list, generating a compare report for
each. You can follow the command verb with one or more -x options
followed by basenames of paths to exclude from comparison. You can get
a context-diff report on file differences with the -u option.</p><p>The 'compare-branches' action takes two repository directories,
extracts a list of branches common to both, then compares the repository
contents at each branch in the list, generating a compare report for
each. You can follow the command verb with one or more -x options
followed by basenames of paths to exclude from comparison. You can get
a context-diff report on file differences with the -u option.</p><p>The 'compare-all' action takes two repository directories, and
runs all 3 above compare actions on them. Even if the same name is a
tag in one repository and a branch in the other, it will compare them
against each other. Not distinguishing them is useful as CVS tags that
are not applied to every file in the repository may get converted to
branches. The options are the same as 'compare-tags'.</p><p>The 'mirror' action makes or updates a local mirror of a
Subversion or CVS repo. It requires a single argument,
either a Subversion URL or a CVS URL, or the name
of a local mirror directory created by a previous run. The first form
creates a local mirror of the repository in a directory named after
the last segment of the URL, with the suffix
<span class="quote">“<span class="quote">-mirror</span>”</span> (the local mirror name can be overridden by an
optional) second argument. The second form updates the local mirror,
doing an incremental fetch; just give the mirror directory
name.</p><p>Subversion URLs are as specified in the public
documentation for Subversion. CVS URLs must specify a host and
repository path, followed by a '#', followed by a module name.</p></div><div class="refsect1"><a name="environment"></a><h2>ENVIRONMENT VARIABLES</h2><p>This program uses the $TMPDIR environment variable, defaulting
to <code class="filename">/tmp</code> if it is not set.</p></div><div class="refsect1"><a name="requirements"></a><h2>REQUIREMENTS</h2><p>
The export action is a wrapper around either native export facilities or the
following engines:
<span class="citerefentry"><span class="refentrytitle">cvs-fast-export</span>(1)</span>
(for CVS),
<span class="citerefentry"><span class="refentrytitle">svnadmin</span>(1)</span>
(for SVN),
<span class="citerefentry"><span class="refentrytitle">hg-fast-export.py</span>(1)</span>
(for hg).
You must have the appropriate engine in your $PATH
for whatever kind of repository you are streaming.
</p></div><div class="refsect1"><a name="see_also"></a><h2>SEE ALSO</h2><p><span class="citerefentry"><span class="refentrytitle">reposurgeon</span>(1)</span>.</p></div><div class="refsect1"><a name="author"></a><h2>AUTHOR</h2><p>Eric S. Raymond <code class="email"><<a class="email" href="mailto:esr@thyrsus.com">esr@thyrsus.com</a>></code>. This tool is
distributed with reposurgeon; see the project page at <a class="ulink" href="http://www.catb.org/~esr/reposurgeon" target="_top">http://www.catb.org/~esr/reposurgeon</a>.</p></div></div></body></html>
|