We use mercurial.
In order to have a meaningful and concise description for each
changeset, we usually split a bug fix or a feature implementation in
multiple changesets. This workflow helps the reviewer as it is clear
what the developer wants to do at each step.
Using post-review to create a
This isn't really possible right now. We've been discussing how we might
support patch series but it's a long-term goal.
There are a few ways that I've seen people cope:
(a) post each change in the series as a successive diff, so you can use
interdiffs to see what changed each time.
(b) post
