Guess it might be easier if I provide the script and associated document
which I'm muttering about here :).
https://docs.google.com/document/d/1z3XtAsVoCx9BDWS8itFZ0mOTd9d66tPus7eSE13m0eM
It's very much a prototype - just knocked up in handful of shell scripts
(I've only included a couple of
On Wednesday, 19 February 2014 16:36:21 UTC+1, Allen wrote:
Really good question!
I also encounter the same problem. Developers dont want to wait until the
previous review passed to work on the next issue.
One solution I think is, once a review passed, apply that review`s patch
file to
On Wednesday, 19 February 2014 21:15:31 UTC+1, David Trowbridge wrote:
The typical way that other dvcs users do this is to have local branches
for each piece of work, and post from each of those. I don't know enough
about bzr's workflow to know if that would be appropriate (though I recall
On Wed, Feb 19, 2014 at 7:36 AM, Allen zhangsan8...@gmail.com wrote:
I have no idea why the review board changes the paths from local to remote
server, at least it should keep the local working copy`s path.
Here`s a example of what those paths look like:
---
Really good question!
I also encounter the same problem. Developers dont want to wait until the
previous review passed to work on the next issue.
One solution I think is, once a review passed, apply that review`s patch
file to a new working copy without touching what you are currently working
The typical way that other dvcs users do this is to have local branches for
each piece of work, and post from each of those. I don't know enough about
bzr's workflow to know if that would be appropriate (though I recall bzr
branches being pretty heavyweight).
-David
On Feb 15, 2014, at 12:51
Is there any documentation for this post-review script?
Where should this script run? In my case we are using a linux server
for review-board and have windows-client where we are working on our
code (svn working base is on windows). Does this script fit into this
environment?
Do I have the