From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/7] package/perl-mailtools: bump to version 2.21
Date: Tue, 17 Sep 2019 22:30:21 +0200 [thread overview]
Message-ID: <20190917223021.2e44b710@windsurf> (raw)
In-Reply-To: <20190917181624.29378-5-francois.perrad@gadz.org>
Hello,
On Tue, 17 Sep 2019 20:16:22 +0200
Francois Perrad <fperrad@gmail.com> wrote:
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/perl-mailtools/Config.in | 2 +-
> package/perl-mailtools/perl-mailtools.hash | 6 +++---
> package/perl-mailtools/perl-mailtools.mk | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
Here as well, you changed the license file hash without any
explanation, so I've added some.
However, the license file being used is README, which does not contain
any useful license related information. Using the README.md file would
be a lot more interesting, as it contains:
======
## Copyright and License
Graham Barr wrote most of these components, since 2001 maintained by
Mark Overmeer. Copyright is with these authors.
This project is free software; you can redistribute it and/or modify it
under the same terms as Perl itself.
See <http://dev.perl.org/licenses/>
======
Could you send a patch to use README.md instead of README, and of
course make sure that scancpan will continue to use README.md moving
forward ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-17 20:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:16 [Buildroot] [PATCH 1/7] package/perl-class-method-modifiers: bump to version 2.13 Francois Perrad
2019-09-17 18:16 ` [Buildroot] [PATCH 2/7] package/perl-date-manip: bump to version 6.78 Francois Perrad
2019-09-17 20:24 ` Thomas Petazzoni
2019-09-17 18:16 ` [Buildroot] [PATCH 3/7] package/perl-devel-stacktrace: bump to version 2.04 Francois Perrad
2019-09-17 20:26 ` Thomas Petazzoni
2019-09-17 18:16 ` [Buildroot] [PATCH 4/7] package/perl-file-slurp: bump to version 9999.28 Francois Perrad
2019-09-17 20:28 ` Thomas Petazzoni
2019-09-17 18:16 ` [Buildroot] [PATCH 5/7] package/perl-mailtools: bump to version 2.21 Francois Perrad
2019-09-17 20:30 ` Thomas Petazzoni [this message]
2019-09-17 18:16 ` [Buildroot] [PATCH 6/7] package/perl-net-dns: bump to version 0.56 Francois Perrad
2019-09-17 20:34 ` Thomas Petazzoni
2019-09-17 18:16 ` [Buildroot] [PATCH 7/7] package/perl-role-tiny: bump to version 2.000008 Francois Perrad
2019-09-17 20:35 ` Thomas Petazzoni
2019-09-17 20:24 ` [Buildroot] [PATCH 1/7] package/perl-class-method-modifiers: bump to version 2.13 Thomas Petazzoni
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190917223021.2e44b710@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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