That command would try to post the diff contained in the commit HEAD~1 (so
the diff between HEAD~2..HEAD~2), which may not actually have the changes
you expected. If you want the diff between master~1 and master, you can run
'rbt post master'
-David
On Thu, Dec 11, 2014 at 6:12 AM Kevin Jones
I tried rbt post HEAD~1 to get a diff from the last commit to the master,
but it only caused the error.
-Kevin
On Wed, Dec 10, 2014 at 6:46 PM, David Trowbridge trowb...@gmail.com
wrote:
What commands are you using for your post-commit review?
-David
On Tue, Dec 9, 2014 at 6:57 PM, Kevin
What commands are you using for your post-commit review?
-David
On Tue, Dec 9, 2014 at 6:57 PM, Kevin Jones kjlo...@gmail.com wrote:
Yes. Same hash.
More digging showed that creating a review from a new branch via rbt post
works. Attempting to do a post-commit review is where the error
Greetings,
I'm trying to figure out why a diff, regardless of whether it was created
with local diff tools or rbt, keeps reporting that it can't find a
particular revision of a file in the repository.
Using: Git and reviewboard 2.0.5
What I've tried:
rbt diff
rbt post master changed_branch
Do master and origin/master point to the same thing?
-David
On Tue, Dec 9, 2014 at 10:16 AM, Kevin Jones kjlo...@gmail.com wrote:
Greetings,
I'm trying to figure out why a diff, regardless of whether it was created
with local diff tools or rbt, keeps reporting that it can't find a
Yes. Same hash.
More digging showed that creating a review from a new branch via rbt post
works. Attempting to do a post-commit review is where the error occurs.
-Kevin
On Tue, Dec 9, 2014 at 4:46 PM, David Trowbridge trowb...@gmail.com wrote:
Do master and origin/master point to the same
