Re: Issue 1673 in reviewboard: post-review revision-range doesn't handle single revision as advertised

2010-11-08 Thread reviewboard
Comment #3 on issue 1673 by phillipb30: post-review revision-range doesn't handle single revision as advertised http://code.google.com/p/reviewboard/issues/detail?id=1673 I've noticed this as well. With SVN it looks like its running svn diff --diff-cmd=diff -r 24 when it should run svn dif

Re: Issue 1874 in reviewboard: post-review does not properly parse diffs between commits in a branch on a git-svn repository

2010-11-08 Thread reviewboard
Comment #3 on issue 1874 by jormon: post-review does not properly parse diffs between commits in a branch on a git-svn repository http://code.google.com/p/reviewboard/issues/detail?id=1874 post-review --debug -n --parent=HEAD^ svn info git rev-parse --git-dir git symbolic-ref -q HEAD git sv

Re: Issue 1874 in reviewboard: post-review does not properly parse diffs between commits in a branch on a git-svn repository

2010-11-08 Thread reviewboard
Comment #2 on issue 1874 by jormon: post-review does not properly parse diffs between commits in a branch on a git-svn repository http://code.google.com/p/reviewboard/issues/detail?id=1874 post-review --debug -n --parent=HEAD^ svn info git rev-parse --git-dir git symbolic-ref -q HEAD git sv

Re: Issue 1684 in reviewboard: Error: Please correct the error below

2010-11-08 Thread reviewboard
Comment #6 on issue 1684 by lukasz.romanowski: Error: Please correct the error below http://code.google.com/p/reviewboard/issues/detail?id=1684 path to repo in RB must be path to .git directory in your repo (/path/to/project/.git/) or repo must be clone with --bare options -- You receive

Issue 1878 in reviewboard: post-review does not parse out user from subversion URL: svn://user@svn_repos

2010-11-08 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1878 by jlbrogdon: post-review does not parse out user from subversion URL: svn://u...@svn_repos http://code.google.com/p/reviewboard/issues/detail?id=1878 *NOTE: Do not post confidential information in this bug report.* W