From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/ed: Bump to version 1.16
Date: Tue, 17 Mar 2020 22:51:21 +0100 [thread overview]
Message-ID: <20200317215121.GX19677@scaer> (raw)
In-Reply-To: <20200310081637.3288-1-kevin.lhopital@bootlin.com>
K?vin, All,
On 2020-03-10 09:16 +0100, K?vin L'h?pital spake thusly:
> Signed-off-by: K?vin L'h?pital <kevin.lhopital@bootlin.com>
Thanks for this patch. However I have a very minor comment, see below...
> ---
> package/ed/ed.hash | 4 ++--
> package/ed/ed.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/ed/ed.hash b/package/ed/ed.hash
> index 96c814d3c2..2544676b06 100644
> --- a/package/ed/ed.hash
> +++ b/package/ed/ed.hash
> @@ -1,4 +1,4 @@
> -# From http://lists.gnu.org/archive/html/bug-ed/2019-01/msg00010.html
> -sha256 ad4489c0ad7a108c514262da28e6c2a426946fb408a3977ef1ed34308bdfd174 ed-1.15.tar.lz
> +# From https://lists.gnu.org/archive/html/bug-ed/2020-02/msg00002.html
> +sha256 cfc07a14ab048a758473ce222e784fbf031485bcd54a76f74acfee1f390d8b2c ed-1.16.tar.lz
We're now trying to converge all our hash files to a common coding
style, which is using two spaces btween fields:
sha256 cfc07a14ab048a758473ce222e784fbf031485bcd54a76f74acfee1f390d8b2c ed-1.16.tar.lz
> # Locally calculated
> sha256 f03a12bef9dfb7281864a0dd965166d4f4ec7a66633df2bc72fa4363e57de02c COPYING
Ditto for the hashes for license files.
Care to fix and respin, please?
(Usually, I'd have fixed while applying, but I have understood that it's
part of your baptism of fire, so... ;-] ).
Regards,
Yann E. MORIN.
> diff --git a/package/ed/ed.mk b/package/ed/ed.mk
> index 6ef8f951cf..deb900e283 100644
> --- a/package/ed/ed.mk
> +++ b/package/ed/ed.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -ED_VERSION = 1.15
> +ED_VERSION = 1.16
> ED_SITE = $(BR2_GNU_MIRROR)/ed
> ED_SOURCE = ed-$(ED_VERSION).tar.lz
> ED_LICENSE = GPL-3.0+
> --
> 2.17.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-03-17 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 8:16 [Buildroot] [PATCH] package/ed: Bump to version 1.16 Kévin L'hôpital
2020-03-17 21:51 ` Yann E. MORIN [this message]
2020-03-18 8:17 ` Kévin L'hôpital
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=20200317215121.GX19677@scaer \
--to=yann.morin.1998@free.fr \
--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