| Age | Commit message (Collapse) | Author |
|---|
|
Patch from Ryan Oblak to add support for HTTP Digest Authentication to
post-review. It was really trivial given the work already added in for HTTP
Basic Authentication.
Testing done: This has been tested on my Review Board 1.1 alpha 1 installation
with Digest, Basic, and no authentication.
Reviewed at http://reviews.reviewboard.org/r/1265/
|
|
When adding/changing binary files against a git-svn repository, the binary
files would be filtered out of the diff. We now represent binary files
properly by faking the information in a diff.
Patch by Anthony Cruz.
Reviewed at http://reviews.reviewboard.org/r/1194/
|
|
This adds improved logic for determining the parent branch used when generating
a diff. It will attempt to detect the merge base of the current head, falling
back to defaults if necessary. A tracking branch can be manually specified
too.
The new code attempts the following:
1) Tries to detect the tracking branch for the current HEAD, if possible.
2) If a tracking branch doesn't exist, or is not remote, it will fall back
on 'origin/master'.
3) If the --tracking-branch parameter is specified, this branch will be used
instead of 'origin/master'.
It also provides unit tests for post-review. Right now, these test only
GitClient (in pure Git mode), but new tests can be added down the line for
the rest of post-review.
Patch by Dan Savilonis
Reviewed at http://reviews.reviewboard.org/r/1144/
|
|
Patch from Flavio Castelli. With this patch post-review will support the
revision-range option following the syntax explained at
http://www.review-board.org/docs/manual/dev/users/tools/post-review/#posting-committed-code
Testing done:
I have tested this new feature locally and it works fine.
I have successfully tested the following commands:
post-review --revision-range=rev1:rev2 --guess-summary --guess-description
post-review --revision-range=rev1:rev2 --guess-description
post-review --revision-range=rev1:rev2
post-review --revision-range=rev --guess-summary --guess-description
post-review --revision-range=rev
Reviewed at http://reviews.review-board.org/r/1049/
|
|
This change introduces Repository UUID support to git-svn, allowing
Review Board to match repositories by UUID instead of comparing the
repository name directly.
Patch by Matthew Woehlke.
Reviewed at http://reviews.review-board.org/r/1030/
|
|
improperly check for the os.uname function.
Fixes bug #1280.
|
|
spaces.
Fixes bug #840.
Reviewed at http://reviews.review-board.org/r/815/
|
|
|
|
file path using a "/" instead of "\" on Windows.
This fixes bug #939.
|
|
post-review with invalid cookies.
Fixes bug #808.
Reviewed at http://reviews.review-board.org/r/813/
|
|
|
|
when using post-review.
Reviewed at http://reviews.review-board.org/r/787/
Fixes bug #585
|
|
Since the dawn of time, post-review has lived in the Review Board tree, despite being a client script and not necessarily being needed on the server.
This moves post-review into a new rbtools package, which users will be able to easy_install (easy_install -U RBTools). The simplejson dependency will be fetched, and users won't have to go hunting in SVN for a script.
Over time, I'd like to add new scripts into here (such as one to apply a diff from a review request), and further down the road I'd like to create an "rbapi" (or something) package that contains a Python API for talking to a Review Board server, which rbtools (and post-review) will then use. For now, the goal is to just get post-review moved over.
Reviewed at http://reviews.review-board.org/r/788/
|
