From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: yegorslists--- via buildroot <buildroot@buildroot.org>
Cc: Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/python-ruamel-yaml: new package
Date: Sat, 23 Jul 2022 21:14:41 +0200 [thread overview]
Message-ID: <20220723211441.53c37bb3@windsurf> (raw)
In-Reply-To: <20220510094556.20618-1-yegorslists@googlemail.com>
On Tue, 10 May 2022 11:45:56 +0200
yegorslists--- via buildroot <buildroot@buildroot.org> wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> package/Config.in | 1 +
> package/python-ruamel-yaml/Config.in | 8 ++++++++
> package/python-ruamel-yaml/python-ruamel-yaml.hash | 6 ++++++
> package/python-ruamel-yaml/python-ruamel-yaml.mk | 14 ++++++++++++++
> 4 files changed, 29 insertions(+)
> create mode 100644 package/python-ruamel-yaml/Config.in
> create mode 100644 package/python-ruamel-yaml/python-ruamel-yaml.hash
> create mode 100644 package/python-ruamel-yaml/python-ruamel-yaml.mk
Thanks, I applied after fixing two check-package warnings:
package/python-ruamel-yaml/python-ruamel-yaml.hash:6: empty line at end of file
package/python-ruamel-yaml/python-ruamel-yaml.mk:12: line contains trailing whitespace
Best regards,
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:[~2022-07-23 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 9:45 [Buildroot] [PATCH] package/python-ruamel-yaml: new package yegorslists--- via buildroot
2022-07-23 19:14 ` 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=20220723211441.53c37bb3@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--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