Send inn-committers mailing list submissions to
        inn-committers@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-committers
or, via email, send a message with subject or body 'help' to
        inn-committers-requ...@lists.isc.org

You can reach the person managing the list at
        inn-committers-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-committers digest..."


Today's Topics:

   1. INN commit: trunk/include/inn (innconf.h) (INN Commit)
   2. INN commit: trunk/doc/man (libinn.3) (INN Commit)


----------------------------------------------------------------------

Message: 1
Date: Sat, 23 Feb 2013 14:51:56 -0800 (PST)
From: INN Commit <r...@isc.org>
To: inn-committ...@isc.org
Subject: INN commit: trunk/include/inn (innconf.h)
Message-ID: <20130223225156.a468467...@hope.eyrie.org>

    Date: Saturday, February 23, 2013 @ 14:51:55
  Author: eagle
Revision: 9459

innconf: Don't test HAVE_SSL
    
This relieves customers of /usr/include/inn from the need to guess
whether INN was built with SSL support in order to get a header that
matches the installed libraries.

Patch from Richard Kettlewell <r...@terraraq.org.uk>.

Modified:
  trunk/include/inn/innconf.h

-----------+
 innconf.h |    2 --
 1 file changed, 2 deletions(-)

Modified: innconf.h
===================================================================
--- innconf.h   2013-01-16 21:57:16 UTC (rev 9458)
+++ innconf.h   2013-02-23 22:51:55 UTC (rev 9459)
@@ -122,12 +122,10 @@
     unsigned long backofftrigger;  /* Number of postings before triggered */
 
     /* Reading and posting -- SSL and TLS support */
-#ifdef HAVE_SSL
     char *tlscafile;            /* Path to a certificate authority file */
     char *tlscapath;            /* Path to a directory of CA certificates */
     char *tlscertfile;          /* Path to the SSL certificate to use */
     char *tlskeyfile;           /* Path to the key for the certificate */
-#endif /* HAVE_SSL */
 
     /* Monitoring */
     bool doinnwatch;            /* Start innwatch from rc.news? */



------------------------------

Message: 2
Date: Sat, 23 Feb 2013 14:52:34 -0800 (PST)
From: INN Commit <r...@isc.org>
To: inn-committ...@isc.org
Subject: INN commit: trunk/doc/man (libinn.3)
Message-ID: <20130223225234.1fa0467...@hope.eyrie.org>

    Date: Saturday, February 23, 2013 @ 14:52:33
  Author: eagle
Revision: 9460

libinn: remove HeaderFind from documentation

It hasn't existed since 2002...

Patch from Richard Kettlewell <r...@terraraq.org.uk>.

Modified:
  trunk/doc/man/libinn.3

----------+
 libinn.3 |   20 --------------------
 1 file changed, 20 deletions(-)

Modified: libinn.3
===================================================================
--- libinn.3    2013-02-23 22:51:55 UTC (rev 9459)
+++ libinn.3    2013-02-23 22:52:33 UTC (rev 9460)
@@ -16,12 +16,6 @@
 .B "HeaderCleanFrom(from)"
 .B "    char   *from;"
 
-.B "char *"
-.B "HeaderFind(Article, Header, size)"
-.B "    char   *Article;"
-.B "    char   *Header;"
-.B "    int    size;"
-
 .B "FILE *"
 .B "CAopen(FromServer, ToServer)"
 .B "    FILE   *FromServer;"
@@ -167,20 +161,6 @@
 The transformations are simple, based on RFC\ 5536 which limits the format
 of the header.
 .PP
-.I HeaderFind
-searches through
-.I Article
-looking for the specified
-.IR Header .
-.I Size
-should be the length of the header name.
-It returns a pointer to the value of the header, skipping leading whitespace,
-or NULL if the header cannot be found.
-.I Article
-should be a standard C string containing the text of the article; the end
-of the headers is indicated by a blank line \(em two consecutive \en
-characters.
-.PP
 .I CAopen
 and
 .I CAclose



------------------------------

_______________________________________________
inn-committers mailing list
inn-committers@lists.isc.org
https://lists.isc.org/mailman/listinfo/inn-committers

End of inn-committers Digest, Vol 48, Issue 1
*********************************************

Reply via email to