From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: yegorslists@googlemail.com
Cc: buildroot@buildroot.org, Daniel Sangue <daniel.sangue@sangue.ch>
Subject: Re: [Buildroot] [PATCH v2] package/libftdi1: bump to version v1.6rc1-2-g92d657b
Date: Mon, 20 Apr 2026 19:26:47 +0200 [thread overview]
Message-ID: <31e74f0efd38811f853848b233efecdc@free.fr> (raw)
In-Reply-To: <20260420101012.2705454-1-yegorslists@googlemail.com>
On 20/04/2026 12:10, yegorslists--- via buildroot wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-04-20 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 10:10 [Buildroot] [PATCH v2] package/libftdi1: bump to version v1.6rc1-2-g92d657b yegorslists--- via buildroot
2026-04-20 17:26 ` Julien Olivain 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=31e74f0efd38811f853848b233efecdc@free.fr \
--to=buildroot@buildroot.org \
--cc=daniel.sangue@sangue.ch \
--cc=ju.o@free.fr \
--cc=yegorslists@googlemail.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