unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 4/4] Makefile.PL: drop update-copyrights rule
Date: Wed, 15 Feb 2023 08:01:12 +0000	[thread overview]
Message-ID: <20230215080112.1740815-5-e@80x24.org> (raw)
In-Reply-To: <20230215080112.1740815-1-e@80x24.org>

I'm no longer updating them since it's noisy and acceptable
to not have them:

  https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/

I'm tired of being reminded what year it is :<
---
 Makefile.PL | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/Makefile.PL b/Makefile.PL
index 9233ac9d..8de1351f 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -261,11 +261,5 @@ symlink-install : lib/PublicInbox.pm
 pure_all :: lib/PublicInbox.pm
 lib/PublicInbox.pm : FORCE
 	VERSION=\$(VERSION) \$(PERL) -w ./version-gen.perl
-
-update-copyrights :
-	\@case '\$(GNULIB_PATH)' in '') echo >&2 GNULIB_PATH unset; false;; esac
-	git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \\
-		UPDATE_COPYRIGHT_USE_INTERVALS=2 \\
-		xargs \$(GNULIB_PATH)/build-aux/update-copyright
 EOF
 }

      parent reply	other threads:[~2023-02-15  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  8:01 [PATCH 0/4] various doc updates Eric Wong
2023-02-15  8:01 ` [PATCH 1/4] doc: WWW + cgi: favor -netd over -httpd Eric Wong
2023-02-15  8:01 ` [PATCH 2/4] doc: flow: update with newer tools, note forkability Eric Wong
2023-02-15  8:01 ` [PATCH 3/4] doc: extindex update on configuration and union section Eric Wong
2023-02-15  8:01 ` Eric Wong [this message]

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=20230215080112.1740815-5-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).