From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 1/6] index: use v5.12, remove outdated comment
Date: Sat, 16 Nov 2024 07:09:48 +0000 [thread overview]
Message-ID: <20241116070953.2945078-2-e@80x24.org> (raw)
In-Reply-To: <20241116070953.2945078-1-e@80x24.org>
There's no unicode_strings-dependent code in this script, so
v5.12 is safe. The comment about libeatmydata shouldn't be
necessary for -index any longer since we support --no-fsync
nowadays and Xapian 1.4+ is fairly widespread.
---
script/public-inbox-index | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/script/public-inbox-index b/script/public-inbox-index
index a13e44bf..82baa7b4 100755
--- a/script/public-inbox-index
+++ b/script/public-inbox-index
@@ -1,12 +1,9 @@
#!perl -w
-# Copyright (C) 2015-2021 all contributors <meta@public-inbox.org>
+# Copyright (C) all contributors <meta@public-inbox.org>
# License: AGPL-3.0+ <https://www.gnu.org/licenses/agpl-3.0.txt>
# Basic tool to create a Xapian search index for a public-inbox.
-# Usage with libeatmydata <https://www.flamingspork.com/projects/libeatmydata/>
-# highly recommended: eatmydata public-inbox-index INBOX_DIR
-use strict;
-use v5.10.1;
+use v5.12;
use Getopt::Long qw(:config gnu_getopt no_ignore_case auto_abbrev);
my $help = <<EOF; # the following should fit w/o scrolling in 80x24 term:
usage: public-inbox-index [options] INBOX_DIR
next prev parent reply other threads:[~2024-11-16 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 7:09 [PATCH 0/6] v5.12 + autodie cleanups Eric Wong
2024-11-16 7:09 ` Eric Wong [this message]
2024-11-16 7:09 ` [PATCH 2/6] over: use autodie for open Eric Wong
2024-11-16 7:09 ` [PATCH 3/6] lei_blob: use autodie for open + seek Eric Wong
2024-11-16 7:09 ` [PATCH 4/6] admin: autodie chdir + open Eric Wong
2024-11-16 7:09 ` [PATCH 5/6] xapcmd: use autodie for numerous syscalls Eric Wong
2024-11-16 7:09 ` [PATCH 6/6] spamc: autodie for open + sysseek 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=20241116070953.2945078-2-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.
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).