From: Peter Korsgaard <peter@korsgaard.com>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Marcus Hoffmann <buildroot@bubu1.eu>,
Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/4] package/python-ruamel-yaml: fix comment in hash file
Date: Sun, 28 Jul 2024 13:07:16 +0200 [thread overview]
Message-ID: <87wml5u657.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240207170959.2672846-1-buildroot@bubu1.eu> (Marcus Hoffmann via buildroot's message of "Wed, 7 Feb 2024 18:09:53 +0100")
>>>>> "Marcus" == Marcus Hoffmann via buildroot <buildroot@buildroot.org> writes:
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
Committed to 2024.02.x and 2024.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-28 11:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 17:09 [Buildroot] [PATCH 1/4] package/python-ruamel-yaml: fix comment in hash file Marcus Hoffmann via buildroot
2024-02-07 17:09 ` [Buildroot] [PATCH 2/4] support/testing: add new python-ruamel-yaml runtime test Marcus Hoffmann via buildroot
2024-07-12 13:06 ` Thomas Petazzoni via buildroot
2024-07-31 15:38 ` Peter Korsgaard
2024-02-07 17:09 ` [Buildroot] [PATCH 3/4] package/python-ruamel-yaml-clib: new package Marcus Hoffmann via buildroot
2024-07-12 13:23 ` Thomas Petazzoni via buildroot
2024-02-07 17:09 ` [Buildroot] [PATCH 4/4] package/python-ruamel-yaml: bump to version 0.18.5 Marcus Hoffmann via buildroot
2024-07-12 13:23 ` Thomas Petazzoni via buildroot
2024-07-12 13:05 ` [Buildroot] [PATCH 1/4] package/python-ruamel-yaml: fix comment in hash file Thomas Petazzoni via buildroot
2024-07-28 11:07 ` Peter Korsgaard [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=87wml5u657.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@bubu1.eu \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.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