Eric Rescorla <[email protected]> wrote: >> For simple reversal or approval, and for longer actual comments (e.g. >> "Thanks for catching this." or "Don't forget to apply this change >> throughout the document." or so), that works fine. >> >> > Just to be clear, if the authors want to make unsolicited changes beyond >> > what the RPC changed, they should be generating their own PRs, not making >> > those changes to the RPC's PR. >> >> If they want to make changes to other pieces of the document (e.g. to >> address issues that haven't been dealt with before), that makes sense. >> >> But for tweaks to the edits from the RPC, commits on top of the RPC's >> commits would make the most sense.
> The way to deal with this is GitHub suggestions.
Yes.
We probably need a short video/screencast to educate WG chairs, secretaries
and which can be linked in the AUTH48 note about this. It's a cool feature,
but it's not easily discovered until you've seen it happen.
(I blame Dave Thaler for helping me discover it. I've never been quite the
same since...)
I'll try to do a few screen-cast/captures and I'll post the link to wgchairs.
One of the pain points is that you can't suggest changes to text that was not
modified..
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
