From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Takumi Takahashi <takumiiinn@gmail.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
Mauro Condarelli <mc5686@mclink.it>,
Asaf Kahlon <asafka7@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/python-pygments: support host package
Date: Sat, 30 Sep 2023 21:41:08 +0200 [thread overview]
Message-ID: <20230930214108.387cefce@windsurf> (raw)
In-Reply-To: <20230930190610.752987-1-takumiiinn@gmail.com>
Hello Takumi,
On Sun, 1 Oct 2023 04:06:10 +0900
Takumi Takahashi <takumiiinn@gmail.com> wrote:
> ---
> package/python-pygments/python-pygments.mk | 1 +
> 1 file changed, 1 insertion(+)
Thanks for your patch.
However, could you clarify on why you need a host variant of this
package, and how it gets used?
Also, we require all patches to have a Signed-off-by line from their
author. Without this, we cannot apply patches that are contributed.
Could you send a new version that (1) has an explanation of why you
need a host package and what uses it and (2) has your Signed-off-by
line?
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-09-30 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 19:06 [Buildroot] [PATCH] package/python-pygments: support host package Takumi Takahashi
2023-09-30 19:41 ` Thomas Petazzoni via buildroot [this message]
2023-10-01 3:11 ` Takumi Takahashi
2023-10-01 3:42 ` [Buildroot] [PATCH v2] " Takumi Takahashi
2024-08-06 20:41 ` Thomas Petazzoni via buildroot
-- strict thread matches above, loose matches on Subject: below --
2023-10-01 3:29 [Buildroot] [PATCH] " Takumi Takahashi
2023-10-01 3:37 ` Takumi Takahashi
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=20230930214108.387cefce@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=mc5686@mclink.it \
--cc=takumiiinn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.