On May 17, 2016, at 8:19 AM, Sandra Loosemore wrote:
>
> I thought I remembered mail going by that changes to a release branch require
> RM approval too.
For time to time, the RM can close any release branch at any time for any
reason. :-) For example, a gcc 3.2.x
On 05/17/2016 03:27 AM, Ramana Radhakrishnan wrote:
On Tue, May 17, 2016 at 1:22 AM, Sandra Loosemore
wrote:
On 05/16/2016 04:35 PM, Jim Wilson wrote:
This is my fifth ping. I just need someone to rubber stamp it so I
can check it in.
The documentation change
On Tue, May 17, 2016 at 1:22 AM, Sandra Loosemore
wrote:
> On 05/16/2016 04:35 PM, Jim Wilson wrote:
>>
>> This is my fifth ping. I just need someone to rubber stamp it so I
>> can check it in.
>
>
> The documentation change looks fine, but as a documentation maintainer
On May 16, 2016, at 5:22 PM, Sandra Loosemore wrote:
>
> On 05/16/2016 04:35 PM, Jim Wilson wrote:
>> This is my fifth ping. I just need someone to rubber stamp it so I
>> can check it in.
>
> The documentation change looks fine, but as a documentation maintainer only
Or, you can cc Jason directly, and ping it. His mailbox filtering has him
reading a subset of the patches emails, (those with C++ as I recall), so this
is likely the first time he has seen it.
> On May 16, 2016, at 3:35 PM, Jim Wilson wrote:
>
> This is my fifth ping.
On 05/16/2016 04:35 PM, Jim Wilson wrote:
This is my fifth ping. I just need someone to rubber stamp it so I
can check it in.
The documentation change looks fine, but as a documentation maintainer
only I don't think I can approve changes to a release branch.
-Sandra
This is my fifth ping. I just need someone to rubber stamp it so I
can check it in.
Maybe it would be easier if I volunteered to be a doc maintainer so I
can self approve it?
Jim
On Mon, May 9, 2016 at 4:21 PM, Jim Wilson wrote:
> On Mon, May 2, 2016 at 12:13 PM, Jim