Comment #7 on issue 921 by erik.l...@gmail.com: Add post-commit review
submission to post-review for perforce
http://code.google.com/p/reviewboard/issues/detail?id=921
I don't think this change actually solves the problem. When you list a
single CLN, it appears to treat it as a range of
Updates:
Status: Fixed
Comment #6 on issue 921 by trowb...@gmail.com: Add post-commit review
submission to post-review for perforce
http://code.google.com/p/reviewboard/issues/detail?id=921
This is now implemented in rbtools master (9ba6c27). When we release
rbtools 0.6, it'll be
Updates:
Status: PendingReview
Owner: trowb...@gmail.com
Comment #5 on issue 921 by trowb...@gmail.com: Add post-commit review
submission to post-review for perforce
http://code.google.com/p/reviewboard/issues/detail?id=921
(No comment was entered for this change.)
--
You
Comment #3 on issue 921 by trowb...@gmail.com: Add post-commit review
submission to post-review for perforce
http://code.google.com/p/reviewboard/issues/detail?id=921
Issue 1747 has been merged into this issue.
--
You received this message because you are subscribed to the Google Groups
Updates:
Summary: Add post-commit review submission to post-review for perforce
Labels: -Type-Defect Type-Enhancement
Comment #2 on issue 921 by trowbrds: Add post-commit review submission to
post-review for perforce
http://code.google.com/p/reviewboard/issues/detail?id=921
