[tahoe-dev] dev workflow: how to go from a patch to its review?
David-Sarah Hopwood
david-sarah at jacaranda.org
Tue Nov 20 07:32:10 UTC 2012
On 20/11/12 06:50, David-Sarah Hopwood wrote:
> On 19/11/12 17:34, Zooko Wilcox-O'Hearn wrote:
>> Thanks, David-Sarah, and I'll follow up on those particular patches
>> via github comments.
>>
>> But, this doesn't answer my question, which is: how can you (a) tell
>> if a patch has been reviewed, and (b) find the review comments?
>>
>> I guess one answer would be: all reviews get posted to github
>> comment-on-the-patch, so then you can, when inspecting the patch, look
>> for comments on it on github. Would that work?
>
> That would work for me provided there is some way to extract all the
> comments from github and back them up.
Oh, github will email the owner of the repo (I think) whenever there is
a comment on a commit. So that email archive is a backup of all comments.
--
David-Sarah Hopwood ⚥
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20121120/e06d0921/attachment.pgp>
More information about the tahoe-dev
mailing list