From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Baruch Siach via buildroot <buildroot@buildroot.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/picocom: bump to version 2023-04
Date: Thu, 4 Jan 2024 22:44:44 +0100 [thread overview]
Message-ID: <20240104224444.76c7800d@windsurf> (raw)
In-Reply-To: <7bf9e3705b3b2bfe8d7796551156abd2ddb8ea26.1704300546.git.baruch@tkos.co.il>
On Wed, 3 Jan 2024 18:49:06 +0200
Baruch Siach via buildroot <buildroot@buildroot.org> wrote:
> Switch to new upstream.
>
> Drop upstream patch.
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> .checkpackageignore | 1 -
> ...-with-libc-s-without-cispeed-cospeed.patch | 49 -------------------
> package/picocom/Config.in | 2 +-
> package/picocom/picocom.hash | 2 +-
> package/picocom/picocom.mk | 4 +-
> 5 files changed, 4 insertions(+), 54 deletions(-)
> delete mode 100644 package/picocom/0001-Compile-with-libc-s-without-cispeed-cospeed.patch
Applied to master, thanks. However, it looks like release-monitoring
isn't aware of this new upstream, at least based on
https://release-monitoring.org/project/3634/. Perhaps something you
could contribute to release-monitoring.org?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-04 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 16:49 [Buildroot] [PATCH] package/picocom: bump to version 2023-04 Baruch Siach via buildroot
2024-01-04 21:44 ` Thomas Petazzoni via buildroot [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240104224444.76c7800d@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=thomas.petazzoni@bootlin.com \
/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