@PLUGIN@ export
===============

NAME
----
@PLUGIN@ export - Export successful reviews to [refs/notes/review](refs-notes-review.html)

SYNOPSIS
--------
```
ssh -p @SSH_PORT@ @SSH_HOST@ @PLUGIN@ export
  [--threads <N>]
```

DESCRIPTION
-----------
Scans every submitted change and creates an initial notes
branch detailing the previous submission information for
each merged change.

This task can take quite some time, but can run in the background
concurrently to the server if the database is MySQL or PostgreSQL.
If the database is H2, this task must be run by itself.

ACCESS
------
Caller must be a member of the privileged 'Administrators' group.

OPTIONS
-------

`--threads <N>`
: Number of concurrent threads to run. By default 2.

CONTEXT
-------
This command can only be run on a server which has direct
connectivity to the metadata database, and local access to the
managed Git repositories.

EXAMPLES
--------
To generate all review information:

```
  $ java -jar gerrit.war ExportReviewNotes -d site_path --threads 16
```

@PLUGIN@ export
===============

NAME
----
@PLUGIN@ export - Export successful reviews to [refs/notes/review](refs-notes-review.html)

SYNOPSIS
--------
```
ssh -p @SSH_PORT@ @SSH_HOST@ @PLUGIN@ export
  [--threads <N>]
```

DESCRIPTION
-----------
Scans every submitted change and creates an initial notes
branch detailing the previous submission information for
each merged change.

This task can take quite some time, but can run in the background
concurrently to the server if the database is MySQL or PostgreSQL.
If the database is H2, this task must be run by itself.

ACCESS
------
Caller must be a member of the privileged 'Administrators' group.

OPTIONS
-------

`--threads <N>`
: Number of concurrent threads to run. By default 2.

CONTEXT
-------
This command can only be run on a server which has direct
connectivity to the metadata database, and local access to the
managed Git repositories.

EXAMPLES
--------
To generate all review information:

```
  $ ssh -p 29418 user@review reviewnotes export --threads 16
```

Correct example of export command usage in documentation
Correct example of export command usage in documentation

The documentation was showing the old style command invocation
from when the review notes export was done with a server program.

Change the example to show usage via the plugin's ssh command.

Change-Id: Iecdb73d9e6b331960a5c9ae8017a22694e912e11
