On 11/17/2016 10:43 AM, Dicebot wrote:
Yes. Assuming you do want multiple review iterations support, I can
imagine something like this:
- new "review candidate #" field is added to the header
- it is set to 0 on initial merge and to 1 after incorporating initial
NG feedback
- it also references
On 11/17/2016 04:36 PM, Andrei Alexandrescu wrote:
> On 11/17/2016 09:16 AM, Dicebot wrote:
>> 2) It is a regular update. In that case revision number is simply git
>> history. For example DIP1002 is currently at revision 7 (git log
>> --pretty=oneline DIPs/DIP1002.md | wc -l).
>>
>> Same goes for
On 11/17/2016 09:16 AM, Dicebot wrote:
2) It is a regular update. In that case revision number is simply git
history. For example DIP1002 is currently at revision 7 (git log
--pretty=oneline DIPs/DIP1002.md | wc -l).
Same goes for update of reviews - everything is tracked in git history.
At any
