> So with this process, you want to continually
> update an existing review request, and you want it to incorporate the new
> updates alongside the existing ones? So if it's already created with a diff
> modifying 5 files, the next update that adds 2 files will result in a diff
> containing a total
Hi Ryan,
Been out of town the past few days, so I'm catching up on e-mail now.
Okay, so I think I understand. So with this process, you want to continually
update an existing review request, and you want it to incorporate the new
updates alongside the existing ones? So if it's already created wit
Ok, let me clarify with a concrete scenario.
We use JIRA for our bug tracking. JIRA generates bug IDs such as
"BUG-123". We also have Hudson for continuous integration, and it's
tied to Perforce to poll for changes, build the changes, and log the
changelists in the build (for release notes). Ou
Hi,
So I'm not 100% sure I understood correctly, but I assume this is related to
the bug you just filed.
--revision-range is not supported on Perforce, but equivalent functionality
does exist. You can use the Perforce path syntax containing revision ranges,
as shown here:
http://www.reviewboard.
