I missed this e-mail completely, sorry about that.
What I am implementing is Git patch series, that is formatted like a
mailbox. It's pretty simple. You can read more about it here:
Cheers, and sorry about the delay.
On Sat, Jun 26, 2010 at 5:59 PM, Christian Hammond <chip...@chipx86.com> wrote:
> Eduardo's working on this for Summer of code. He can hopefully fill you in
> on the plans. Right now, there's no public code that I'm aware of.
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
> On Thu, Jun 24, 2010 at 4:14 AM, Stephen Gallagher
> <step...@gallagherhome.com> wrote:
>> On 06/24/2010 02:43 AM, Christian Hammond wrote:
>>> The way Review Board handles diffs today is that every revision of the
>>> diff is meant to be a single change, from the base to the tip of the branch.
>>> What I think you're wanting (please correct me if I'm wrong) is more of a
>>> patchset concept, with each diff being an iteration of a change. This
>>> workflow is not supported yet, but we have a Summer of Code student working
>>> on it.
>> Is there a public specification available on how these patchsets are going
>> to be supported? What about a public repository to follow the changes? This
>> is highly relevant to my interests :)
>> Want to help the Review Board project? Donate today at
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> To unsubscribe from this group, send email to
>> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at