From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/6] doc updates and such
Date: Wed, 1 Jan 2020 09:57:49 +0000 [thread overview]
Message-ID: <20200101095755.31325-1-e@80x24.org> (raw)
More frequent releases should be possible, now that we can just
let cgit serve our tar.gz. Maybe Plack/PSGI can be totally
optional, even for WWW... The closure purge certainly brought
us in that direction :>
Eric Wong (6):
doc: allow NEWS file to be built without Plack::Util
build: remove NEWS from dist-git target
doc: release notes: set Date for 1.2.0, start 1.3.0
doc/txt2pre: flush output before utime()
build: fix xapian-* manpage generation
doc: fix a few spelling errors in user-facing docs
Documentation/RelNotes/v1.2.0.eml | 9 +++++
Documentation/RelNotes/v1.3.0.eml | 50 +++++++++++++++++++++++++++
Documentation/include.mk | 23 ++++++------
Documentation/mknews.perl | 30 ++++++++++++----
Documentation/public-inbox-config.pod | 2 +-
Documentation/public-inbox-nntpd.pod | 2 +-
Documentation/txt2pre | 1 +
MANIFEST | 1 +
Makefile.PL | 3 +-
lib/PublicInbox/Import.pm | 2 +-
10 files changed, 100 insertions(+), 23 deletions(-)
create mode 100644 Documentation/RelNotes/v1.3.0.eml
next reply other threads:[~2020-01-01 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 9:57 Eric Wong [this message]
2020-01-01 9:57 ` [PATCH 1/6] doc: allow NEWS file to be built without Plack::Util Eric Wong
2020-01-01 9:57 ` [PATCH 2/6] build: remove NEWS from dist-git target Eric Wong
2020-01-01 9:57 ` [PATCH 3/6] doc: release notes: set Date for 1.2.0, start 1.3.0 Eric Wong
2020-01-01 9:57 ` [PATCH 4/6] doc/txt2pre: flush output before utime() Eric Wong
2020-01-01 9:57 ` [PATCH 5/6] build: fix xapian-* manpage generation Eric Wong
2020-01-01 9:57 ` [PATCH 6/6] doc: fix a few spelling errors in user-facing docs Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200101095755.31325-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).