[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNITS being referenced, with no link...

From: Ralf Wildenhues
Subject: Re: GNITS being referenced, with no link...
Date: Fri, 7 Sep 2007 04:52:16 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

[ <> ]

Hello Alfred,

Sorry for the very long delay, I just stumbled over your mail again.

* Alfred M. Szmidt wrote on Tue, Jan 03, 2006 at 11:46:41PM CET:
> The GNITS is being referenced in the automake manual, but with no link
> to it!  GNITS was usually quite a internal thing, but I dug it up from
> the dead a while a go (got a copy from Franc,ois Pinard many years ago
> I think); and now a copy--which has only had some structural changes
> so that it is in sync with the layout for the GNU Coding Standards--is
> avaiable in the GNU womb project.
> I just commited the generated HTML pages for GNITS, so they should be
> avaiable from shortly (the
> top-level directory has no content yet).

The GNITS manual does have several links to the GCS, but none of the
HTML references work.  ;-)

For example, in
<> there is a
reference to
You should be able to fix that with some addition to the womb/.symlinks

How about the patch below (for HEAD and branch-1-5)?
Barring objections, I'll apply in a few days.


2007-09-07  Ralf Wildenhues  <address@hidden>

        * doc/automake.texi (Strictness, Gnits): Add URL to Gnits
        Report by Alfred M. Szmidt.

Index: doc/automake.texi
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.171
diff -u -r1.171 automake.texi
--- doc/automake.texi   19 Aug 2007 07:46:52 -0000      1.171
+++ doc/automake.texi   7 Sep 2007 02:50:29 -0000
@@ -1818,11 +1818,12 @@
 standards for packages.  This is the default.
 @item gnits
-Automake will check for compliance to the as-yet-unwritten @dfn{Gnits
+Automake will check for compliance to the as-yet-unfinished @dfn{Gnits
 standards}.  These are based on the GNU standards, but are even more
 detailed.  Unless you are a Gnits standards contributor, it is
 recommended that you avoid this option until such time as the Gnits
-standard is actually published (which may never happen).
+standard is actually finished (which may never happen).  See
address@hidden://} for more information.
 @end table
 @xref{Gnits}, for more information on the precise implications of the
@@ -8959,8 +8960,7 @@
 @code{VERSION} is checked to make sure its format complies with Gnits
address@hidden FIXME xref when standards are finished
+standards, see @uref{}.
 @cindex @file{README-alpha}

reply via email to

[Prev in Thread] Current Thread [Next in Thread]