From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 5/9] gcf2: rely on Perl 5.10 to avoid needless ++
Date: Wed, 27 Jan 2021 03:42:26 -0600 [thread overview]
Message-ID: <20210127094230.31174-6-e@80x24.org> (raw)
In-Reply-To: <20210127094230.31174-1-e@80x24.org>
And note the PublicInbox::Spawn side effect of setting
PERL_INLINE_DIRECTORY.
---
lib/PublicInbox/Gcf2.pm | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/lib/PublicInbox/Gcf2.pm b/lib/PublicInbox/Gcf2.pm
index 01b83c96..99f4ae04 100644
--- a/lib/PublicInbox/Gcf2.pm
+++ b/lib/PublicInbox/Gcf2.pm
@@ -5,7 +5,8 @@
# other libgit2 stuff may go here, too.
package PublicInbox::Gcf2;
use strict;
-use PublicInbox::Spawn qw(which popen_rd);
+use v5.10.1;
+use PublicInbox::Spawn qw(which popen_rd); # may set PERL_INLINE_DIRECTORY
use Fcntl qw(LOCK_EX);
use IO::Handle; # autoflush
my (%CFG, $c_src, $lockfh);
@@ -73,6 +74,7 @@ sub add_alt ($$) {
$gcf2->add_alternate($_) for @abs_alt;
}
$gcf2->add_alternate($objdir);
+ 1;
}
# Usage: $^X -MPublicInbox::Gcf2 -e PublicInbox::Gcf2::loop
@@ -86,7 +88,7 @@ sub loop () {
while (<STDIN>) {
chomp;
my ($oid, $git_dir) = split(/ /, $_, 2);
- $seen{$git_dir}++ or add_alt($gcf2, "$git_dir/objects");
+ $seen{$git_dir} //= add_alt($gcf2, "$git_dir/objects");
if (!$gcf2->cat_oid(1, $oid)) {
# retry once if missing. We only get unabbreviated OIDs
# from SQLite or Xapian DBs, here, so malicious clients
@@ -94,8 +96,7 @@ sub loop () {
warn "I: $$ $oid missing, retrying in $git_dir\n";
$gcf2 = new();
- %seen = ($git_dir => 1);
- add_alt($gcf2, "$git_dir/objects");
+ %seen = ($git_dir => add_alt($gcf2,"$git_dir/objects"));
if ($gcf2->cat_oid(1, $oid)) {
warn "I: $$ $oid found after retry\n";
next prev parent reply other threads:[~2021-01-27 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:42 [PATCH 0/9] lei completion, some small updates Eric Wong
2021-01-27 9:42 ` [PATCH 1/9] eml: favor index() over regexp match Eric Wong
2021-01-27 9:42 ` [PATCH 2/9] lei: drop "git" command forwarding Eric Wong
2021-01-27 9:42 ` [PATCH 3/9] lei: fix comment regarding client payload Eric Wong
2021-01-27 9:42 ` [PATCH 4/9] lei: set PWD correctly for path expansion Eric Wong
2021-01-27 9:42 ` Eric Wong [this message]
2021-01-27 9:42 ` [PATCH 6/9] lei: complete option switch args Eric Wong
2021-01-27 9:42 ` [PATCH 7/9] lei_overview: clear redundant ovv_buf definition Eric Wong
2021-01-27 9:42 ` [PATCH 8/9] v2writable: nproc: use sysconf() on Linux and FreeBSD Eric Wong
2021-01-27 9:42 ` [PATCH 9/9] lei: dclose: fix typo 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=20210127094230.31174-6-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).