Re: Document hardening flags in the coding standards

[Karl Berry]

First: rms asked "what do they do?".

And I guess that is what I am wondering too, to find the right place.

    neither manual would give readers the full picture.  

>From the user's point of view, the split between gcc and glibc for this
purpose seems nearly arbitrary.  So you could just choose one for the
full explanation and link from the other.

    That's why I was looking for a place to put the combined
    documentation.

Well, the coding standards doesn't seem like the place for the primary
documentation of a gcc/glibc/kernel/whatever feature.  If someone says
"how do I use GCC to make my program more secure", it doesn't seem like
the answer should be in standards.texi.

We do have another document for "GNU Quality Code" -- it never got very
far, but it does exist:
http://www.gnu.org/software/gnustandards/qualitycode.html.  If you don't
think the package documentation is preferable, perhaps that's a
possibility.

There'd also be no problem giving as many people write access to that
document as you like, whereas standards.texi commits are more
controlled.

Best,
Karl