user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [PUSHED] run update-copyrights from gnulib for 2019
Date: Mon, 9 Sep 2019 05:57:10 +0000	[thread overview]
Message-ID: <20190909055710.nhbaijguegmolkwq@whir> (raw)

Too many lines changed to be worth sending a patch for:

 151 files changed, 151 insertions(+), 151 deletions(-)

             reply	other threads:[~2019-09-09  5:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  5:57 Eric Wong [this message]
2020-02-06 19:17 ` [PUSHED] run update-copyrights from gnulib for 2020 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190909055710.nhbaijguegmolkwq@whir \ \ \

* 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

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).