On Sat, Apr 23, 2016 at 01:10:01PM -0400, Cole Robinson wrote:
On 04/22/2016 01:28 AM, Martin Kletzander wrote:
On Thu, Apr 21, 2016 at 10:16:41AM -0400, Cole Robinson wrote:
On 04/21/2016 06:08 AM, Martin Kletzander wrote:
On Wed, Apr 20, 2016 at 07:57:05PM -0400, Cole Robinson wrote:
I'm
On 04/22/2016 01:28 AM, Martin Kletzander wrote:
> On Thu, Apr 21, 2016 at 10:16:41AM -0400, Cole Robinson wrote:
>> On 04/21/2016 06:08 AM, Martin Kletzander wrote:
>>> On Wed, Apr 20, 2016 at 07:57:05PM -0400, Cole Robinson wrote:
I'm looking in the code to see why runtime VM dac seclabel
On Thu, Apr 21, 2016 at 10:16:41AM -0400, Cole Robinson wrote:
On 04/21/2016 06:08 AM, Martin Kletzander wrote:
On Wed, Apr 20, 2016 at 07:57:05PM -0400, Cole Robinson wrote:
I'm looking in the code to see why runtime VM dac seclabel values aren't
printed in the active XML. They are filled in,
On 04/21/2016 06:08 AM, Martin Kletzander wrote:
> On Wed, Apr 20, 2016 at 07:57:05PM -0400, Cole Robinson wrote:
>> I'm looking in the code to see why runtime VM dac seclabel values aren't
>> printed in the active XML. They are filled in, but the domain XML formatter
>> explicitly skips it:
>>
>>
On Wed, Apr 20, 2016 at 07:57:05PM -0400, Cole Robinson wrote:
I'm looking in the code to see why runtime VM dac seclabel values aren't
printed in the active XML. They are filled in, but the domain XML formatter
explicitly skips it:
/* To avoid backward compatibility issues, suppress DAC and
I'm looking in the code to see why runtime VM dac seclabel values aren't
printed in the active XML. They are filled in, but the domain XML formatter
explicitly skips it:
/* To avoid backward compatibility issues, suppress DAC and 'none' labels
* that are automatically generated.
*/
