From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] Makefile.PL: fix useless use of push
Date: Mon, 6 Dec 2021 20:55:59 +0000 [thread overview]
Message-ID: <20211206205559.2173-1-e@80x24.org> (raw)
---
Makefile.PL | 1 -
1 file changed, 1 deletion(-)
diff --git a/Makefile.PL b/Makefile.PL
index cde6194bc54a..28e51ffa0f08 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -92,7 +92,6 @@ for my $i (@sections) {
push @{$v->{manuals}}, @$manuals;
push @{$v->{mantxt}}, map { "Documentation/$_.txt" } @$ary;
}
-push @dtxt;
$v->{docs} = [ @dtxt, 'NEWS' ];
$v->{docs_html} = [ map {;
my $x = $_;
reply other threads:[~2021-12-06 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211206205559.2173-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.
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).