Send inn-committers mailing list submissions to
        [email protected]

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
        [email protected]

You can reach the person managing the list at
        [email protected]

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


Today's Topics:

   1. [InterNetNews/inn] 542cbf: Wrap long lines for man pages in
      POD documentation (Julien ?LIE)
   2. [InterNetNews/inn] 5283c5: Typos in POD documentation
      (Julien ?LIE)
   3. [InterNetNews/inn] 3a6288: Wrap long lines in POD
      documentation (Julien ?LIE)
   4. [InterNetNews/inn] b6894e: Clarify the reload of readers.conf
      on changes (Julien ?LIE)
   5. [InterNetNews/inn] 69a5cf: readers.conf: Homogenize POD style
      (Julien ?LIE)


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

Message: 1
Date: Mon, 20 Feb 2023 09:34:56 -0800
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: [InterNetNews/inn] 542cbf: Wrap long lines for man pages in
        POD documentation
Message-ID:
        <InterNetNews/inn/push/refs/heads/main/[email protected]>
Content-Type: text/plain; charset=UTF-8

  Branch: refs/heads/main
  Home:   https://github.com/InterNetNews/inn
  Commit: 542cbf2878b01dd0cbcded89366ca84401d63739
      
https://github.com/InterNetNews/inn/commit/542cbf2878b01dd0cbcded89366ca84401d63739
  Author: Julien ?LIE <[email protected]>
  Date:   2023-02-20 (Mon, 20 Feb 2023)

  Changed paths:
    M backends/send-uucp.in
    M doc/pod/expire.ctl.pod
    M doc/pod/grephistory.pod
    M doc/pod/hook-perl.pod
    M doc/pod/hook-python.pod
    M doc/pod/innfeed.pod
    M doc/pod/libinn_list.pod
    M doc/pod/libinnhist.pod
    M doc/pod/libinnstorage.pod
    M doc/pod/newsfeeds.pod
    M doc/pod/newslog.pod
    M doc/pod/ninpaths.pod
    M doc/pod/readers.conf.pod
    M perl/INN/Utils/Shlock.pm.in

  Log Message:
  -----------
  Wrap long lines for man pages in POD documentation

A few indented lines were too long to be gracefully displayed in *roff.




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

Message: 2
Date: Mon, 20 Feb 2023 09:37:55 -0800
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: [InterNetNews/inn] 5283c5: Typos in POD documentation
Message-ID:
        <InterNetNews/inn/push/refs/heads/main/[email protected]>
Content-Type: text/plain; charset=UTF-8

  Branch: refs/heads/main
  Home:   https://github.com/InterNetNews/inn
  Commit: 5283c565e510c6019a1ca9c75c1dfe2753a20764
      
https://github.com/InterNetNews/inn/commit/5283c565e510c6019a1ca9c75c1dfe2753a20764
  Author: Julien ?LIE <[email protected]>
  Date:   2023-02-20 (Mon, 20 Feb 2023)

  Changed paths:
    M backends/send-uucp.in
    M doc/pod/inn.conf.pod
    M doc/pod/news.pod
    M doc/pod/newsfeeds.pod
    M doc/pod/readers.conf.pod

  Log Message:
  -----------
  Typos in POD documentation




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

Message: 3
Date: Mon, 20 Feb 2023 09:40:09 -0800
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: [InterNetNews/inn] 3a6288: Wrap long lines in POD
        documentation
Message-ID:
        <InterNetNews/inn/push/refs/heads/main/[email protected]>
Content-Type: text/plain; charset=UTF-8

  Branch: refs/heads/main
  Home:   https://github.com/InterNetNews/inn
  Commit: 3a6288c6f03ede395f38e005c35d80e4fca9fb60
      
https://github.com/InterNetNews/inn/commit/3a6288c6f03ede395f38e005c35d80e4fca9fb60
  Author: Julien ?LIE <[email protected]>
  Date:   2023-02-20 (Mon, 20 Feb 2023)

  Changed paths:
    M doc/pod/controlchan.pod
    M doc/pod/hacking.pod
    M doc/pod/hook-perl.pod
    M doc/pod/hook-python.pod
    M doc/pod/install.pod
    M doc/pod/makedbz.pod
    M doc/pod/mod-active.pod
    M doc/pod/news.pod
    M doc/pod/newslog.pod
    M doc/pod/readers.conf.pod
    M doc/pod/sendinpaths.pod
    M doc/pod/storage.conf.pod

  Log Message:
  -----------
  Wrap long lines in POD documentation

Keep the limit to 79 characters like what we do for the source code.




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

Message: 4
Date: Mon, 20 Feb 2023 09:42:27 -0800
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: [InterNetNews/inn] b6894e: Clarify the reload of readers.conf
        on changes
Message-ID:
        <InterNetNews/inn/push/refs/heads/main/[email protected]>
Content-Type: text/plain; charset=UTF-8

  Branch: refs/heads/main
  Home:   https://github.com/InterNetNews/inn
  Commit: b6894eb7a10c690c4eafac4d79a6d41311a383d1
      
https://github.com/InterNetNews/inn/commit/b6894eb7a10c690c4eafac4d79a6d41311a383d1
  Author: Julien ?LIE <[email protected]>
  Date:   2023-02-20 (Mon, 20 Feb 2023)

  Changed paths:
    M doc/pod/readers.conf.pod

  Log Message:
  -----------
  Clarify the reload of readers.conf on changes

It's not necessary, even with nnrpd run as a daemon.




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

Message: 5
Date: Mon, 20 Feb 2023 09:44:57 -0800
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: [InterNetNews/inn] 69a5cf: readers.conf: Homogenize POD style
Message-ID:
        <InterNetNews/inn/push/refs/heads/main/[email protected]>
Content-Type: text/plain; charset=UTF-8

  Branch: refs/heads/main
  Home:   https://github.com/InterNetNews/inn
  Commit: 69a5cf55eea98b8edf75034df97e7dcdb23337ea
      
https://github.com/InterNetNews/inn/commit/69a5cf55eea98b8edf75034df97e7dcdb23337ea
  Author: Julien ?LIE <[email protected]>
  Date:   2023-02-20 (Mon, 20 Feb 2023)

  Changed paths:
    A doc/pod/readers.conf.pod.NEW

  Log Message:
  -----------
  readers.conf: Homogenize POD style

Proof-read, and apply the style we have in other manual pages.




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

Subject: Digest Footer

_______________________________________________
inn-committers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-committers


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

End of inn-committers Digest, Vol 148, Issue 7
**********************************************

Reply via email to