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
Hi,
We're trying to follow a pre-commit workflow with bzr with all patches
submitted to the review board prior to checkin to the repo - I was
wondering anyone had any experience with this and how best to handle
pending patches.
Sometimes it's inconvenient to wait for the review process to be
