-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Thu, Sep 19, 2013 at 03:20:18PM +0200, Florian Weimer wrote:
> On 09/18/2013 02:50 AM, [email protected] wrote:
> >Repository : http://git.fedorahosted.org/git/?p=secure-coding.git
> >
> >On branch  : master
> >
> >>---------------------------------------------------------------
> >
> >commit 749d19d9ed8385458f3ecffb7df3f25522775e78
> >Author: Eric Christensen <[email protected]>
> >Date:   Tue Sep 17 20:49:59 2013 -0400
> >
> >     Updated POT files
> 
> This includes POT files for the code snippets?  Is this really
> necessary?  Or is this because we want to translate the comments in
> the source files?

I hasn't really noticed that the POT files included the code snippets.  This is 
the first guide I've dealt with that had separate code files.  Translating the 
comments could be useful, though.

> We could move those comments to the main text, I assume, splitting
> up some of the snippets.

Up to you.  I could also just remove those POT files, too.

- -- Eric

- --------------------------------------------------
Eric "Sparks" Christensen
Red Hat, Inc - Product Security Team

[email protected] - [email protected]
097C 82C3 52DF C64A 50C2  E3A3 8076 ABDE 024B B3D1
- --------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQGcBAEBCgAGBQJSOwcfAAoJEB/kgVGp2CYvKDUL+gNpKU7VeuM510UCwXw87GjX
hp8d2868WpvAkGZ/kN9wedbgD4B/+IyPRTE5M+Sxs+935z0EQrkh1sRnPc4VYtqp
fHug7CfJQKVoJnMmPD0kS662IepzeqtP8Krz/XAZljLXTS2OiV1eQfXFLVE492yW
VWALXmTL0zqFTC/2iP6yUb/dW8fl+LN2GqAoJapVxu47YifP/9HxRRukt06Tq4cX
eRfJ0Ub0iOqaY+PQjM+WrghYyAztnul/CCpSYechi5DuyjA6Ew5MC04gsPg9Q8HZ
eZkZGlHrOQdqvyKkv1AkI+IJOOh6h9jdfbogNZudL8kzeStKhxUbip0EUHplBh+N
5zhHjSsXS/ortLx6G+fxLcCoZspEnJT7y04mgic4smCPqD9Wxf0Dm1GAUuLJgQGs
1cdrJ9cWLVrwaQRkpdl/nxvxgj66YqBclzgCF8KFbr0XK5da7FTr8tG+WS7nv/eb
+nW/3PN9JBbwWBgrkrK/Hb4ByTKYBZXWW0rhhbKOdA==
=4Ge7
-----END PGP SIGNATURE-----
--
security mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/security

Reply via email to