Comment #7 on issue 921 by Add post-commit review submission to post-review for perforce

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 CLN-1 and CLN. In Perforce (unlike git) this is not the correct behavior as the two change lists can be completely unrelated. It looks like if you run the code with rbt post CLN CLN, it tries to do the right thing but for some reason isn't generating a diff for edit files, only added files (which p4 describe fails to do).

You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to