Hi David,
Actually I was validating both pre and post-commits.
OK coming to question number 1.
I'm running "rbt post" after the commits using revision number. In rbtools doc
it was mentioned only "rbt post %rev%". I couldn't capture the svn commit
message to pick it for reviews summary and d
What doc are you referring to that says "%rev%"?
rbt post does have --summary and --description parameters.
-David
On Sat, Jul 16, 2016 at 1:57 AM john levin wrote:
> Hi David,
> Actually I was validating both pre and post-commits.
> OK coming to question number 1.
> I'm running "rbt post" afte
Ahhh.. Actually i was parsing like
rbt post REV --summary "TEST" --descriptions "TEST" (i looked the doc, it
says rbt post %REV% for committed files).
and getting Error: Too many revision.
But i didnt noted that summary and descriptions should be passed before the
revisions ( Havent gone throu
David,
For my Second question. I could understand that there is no option to
update reviews in post-commit model (If not, pls help me to find out), then
how can developers will fix the Open Issues ? You mean for Open Issues
again a new review gets created ?
On Saturday, July 16, 2016 at 10:4
John,
Theoretically you could upload the diff of the new commit as a new revision
on an old review request, but the interdiffs won't make sense then. Review
Board expects each revision of the diff to be the entire change. In a
post-commit model, that usually means it's more appropriate for "fix up