Patch by Eric Huss to support posting paths of files to Review Board

when using Perforce. This method doesn't take a change number, but
rather a set of files and optional revisions. His documentation states:

"We have some use cases where it would be nice to review entire files
post-commit in reviewboard.  Some examples:

- Our documentation needs to be checked in before it is reviewed.  If multiple
  people are working on it, or if it is created as a series of multiple
  checkins, reviewing specific change numbers is difficult.  With this, we can
  do "post-review //docs/main/some/project/...".

- If you work on a side branch for a while, possibly with multiple checkins or
  with multiple people, reviewing the changes on the side branch before
  integration to the main branch can be tricky.  With this, you can now do
  "post-review //path/to/my/branch/...@100,@120" where "100" would be the
  initial revision that created the branch and "120" is the last revision on
  that branch.  This allows you to easily review all changes on a branch in one
  review request.

- If you want to review an old, existing file that has had little or no
  reviews, you can now do this with "post-review //path/to/some/file" to review
  the whole thing.

The specific path types supported are:

  post-review //path/to/file
  # Upload file as a "new" file.

  post-review //path/to/dir/...
  # Upload all files as "new" files.

  post-review //path/to/file[@#]rev
  # Upload file from that rev as a "new" file.
  # (Not a very useful scenario, but it works.)

  post-review //path/to/file[@#]rev,[@#]rev
  # Upload a diff between revs.

  post-review //path/to/dir/...[@#]rev,[@#]rev
  # Upload a diff of all files between revs in that directory.

You can specify multiple paths on the command line.  I didn't use the range
revision option because the Perforce path syntax is a little more flexible,
especially if you post multiple paths.

Reviewed at http://reviews.review-board.org/r/753/

0 files changed, 0 insertions, 0 deletions