From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/minicom: bump version
Date: Wed, 1 Jan 2020 20:37:52 +0100 [thread overview]
Message-ID: <20200101193752.GO3519@scaer> (raw)
In-Reply-To: <20200101174014.37595-1-giulio.benetti@benettiengineering.com>
Giulio, All,
On 2020-01-01 18:40 +0100, Giulio Benetti spake thusly:
> Shortlog follows:
> Adam Lackorzynski (2):
> minicom.c: Convert TABs to spaces
> minicom.c: Reflow long_options
>
> Rasmus Villemoes (1):
> Allow user to specify buffering mode of capture file
tHe complete changelog is not so initeresting to have as a commit log.
Rather, only the important changes, if any, should be mentioned, like
security fixes or big new feats. In this case, nothing really stands
out, really, but I jsut kept is anyway...
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/minicom/minicom.hash | 2 +-
> package/minicom/minicom.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/minicom/minicom.hash b/package/minicom/minicom.hash
> index 03e1dcc7d0..9725f58f6d 100644
> --- a/package/minicom/minicom.hash
> +++ b/package/minicom/minicom.hash
> @@ -1,3 +1,3 @@
> # Locally calculated
> -sha256 be5d923c399bc15dade7bc89052d887034abd49b386138c16bdcb912f2135098 minicom-5086119bbaafd2f8986579209885635b92020096.tar.gz
> +sha256 c8e34cc583f3b09c65871f5080b04799895b1ebd72092c0e18cb20a631f6c4b1 minicom-a6a507dcb8bd4cb5da7af9e2dc75b8e495fedbb6.tar.gz
> sha256 cf80a758014eefbf068afffe3d462fc34ff4f528527524d8e100329c42094e15 COPYING
> diff --git a/package/minicom/minicom.mk b/package/minicom/minicom.mk
> index c08e9b10f4..a86d587b2f 100644
> --- a/package/minicom/minicom.mk
> +++ b/package/minicom/minicom.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -MINICOM_VERSION = 5086119bbaafd2f8986579209885635b92020096
> +MINICOM_VERSION = a6a507dcb8bd4cb5da7af9e2dc75b8e495fedbb6
> MINICOM_SITE = https://salsa.debian.org/minicom-team/minicom.git
> MINICOM_SITE_METHOD = git
> MINICOM_LICENSE = GPL-2.0+
> --
> 2.20.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-01-01 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 17:40 [Buildroot] [PATCH] package/minicom: bump version Giulio Benetti
2020-01-01 19:37 ` Yann E. MORIN [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-02 17:25 Giulio Benetti
2020-12-05 21:03 ` Thomas Petazzoni
2020-02-09 20:44 Giulio Benetti
2020-02-09 20:44 ` Giulio Benetti
2020-02-09 20:47 ` Giulio Benetti
2020-02-16 16:17 ` Peter Korsgaard
2019-10-04 20:51 Giulio Benetti
2019-10-05 21:10 ` 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=20200101193752.GO3519@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