Re: Soliciting feedback for the GLSA-2 format

--Apple-Mail=_44319C43-1E29-4911-9E4C-0D2D27311FC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

That is the part that would be the most important, as the XML makes =
sense to me. The translation from XML to GLSA would be the most =
important part so that it is clear to the general populace.

Whenever I write things for work I am always using the rule of writing =
to the least common denominator, and I can see this part being the most =
confusing.

Yury German
E-Mail: [email protected]

PGP/GPG ID: 19EC14B3



On Jan 9, 2014, at 8:35 PM, Tobias Heinlein <[email protected]> =
wrote:

> On 10.01.2014 00:37, Yury German wrote:
>> is this what the users will see as generated from XML?
>=20
> That was just a short example explaining the semantics of the new =
syntax.
>=20
> We haven't discussed yet how it'll show up in the text advisory, =
probably something like "Slot 3.2: <3.2.1 >3.4.2".
>=20
>=20


--Apple-Mail=_44319C43-1E29-4911-9E4C-0D2D27311FC2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iEYEARECAAYFAlLPXisACgkQc57wrRnsFLOxvACfSKp2eR/VFyNS+yt5m8i4hOP6
1bwAoKVbP3QWMdkOPsqr2GiwNskU9zkc
=Kh23
-----END PGP SIGNATURE-----

--Apple-Mail=_44319C43-1E29-4911-9E4C-0D2D27311FC2--