We think that the best thing to do is to keep the ostream_guard in place and
ignore the "Restore ostream format" issues.
-Original Message-
From: Chris Johns
Sent: Wednesday, August 4, 2021 8:44 PM
To: Gedare Bloom
Cc: Ryan Long ; devel@rtems.org
Subject: Re: [PATCH v1
On 5/8/21 9:13 am, Gedare Bloom wrote:
> On Wed, Aug 4, 2021 at 4:47 PM Chris Johns wrote:
>>
>> On 5/8/21 1:54 am, Ryan Long wrote:
>>> ostream_guard did not fix the "Not restoring ostream format" Coverity
>>> issues as hoped, so there's no reason to have it.
>>
>> Can you capture the missing pie
On Wed, Aug 4, 2021 at 4:47 PM Chris Johns wrote:
>
> On 5/8/21 1:54 am, Ryan Long wrote:
> > ostream_guard did not fix the "Not restoring ostream format" Coverity
> > issues as hoped, so there's no reason to have it.
>
> Can you capture the missing pieces here?
>
Also, just because it didn't fix
On 5/8/21 1:54 am, Ryan Long wrote:
> ostream_guard did not fix the "Not restoring ostream format" Coverity
> issues as hoped, so there's no reason to have it.
Can you capture the missing pieces here?
Chris
___
devel mailing list
devel@rtems.org
http://
ostream_guard did not fix the "Not restoring ostream format" Coverity
issues as hoped, so there's no reason to have it.
---
rtemstoolkit/rtems-utils.h | 20
1 file changed, 20 deletions(-)
diff --git a/rtemstoolkit/rtems-utils.h b/rtemstoolkit/rtems-utils.h
index 81bf913..4ce
