From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nevo Hed <nhed+buildroot@starry.com>
Cc: Nevo Hed via buildroot <buildroot@buildroot.org>,
Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] utils/generate-cyclonedx: fix monotonically increasing dependency list
Date: Wed, 3 Dec 2025 08:46:14 +0100 [thread overview]
Message-ID: <20251203084614.3b7525c5@windsurf> (raw)
In-Reply-To: <CABGDZC=R0ndhtoyhdFrzmDs6HgVXGoVhrUAODOqfOLgnBX8NQA@mail.gmail.com>
On Tue, 2 Dec 2025 16:34:55 -0500
Nevo Hed <nhed+buildroot@starry.com> wrote:
> Yeah sorry about that - I rarely contribute here and am very much in the
> github pull-request mode
No worries!
>
> I will add that and try to reformat the v2
>
> Just one question - do I include or drop the `Reviewed-by: Thomas Perale <
> thomas.perale@mind.be>` line? (In my local repo I had updated from the
> patchworks)?
If you got a reviewed-by, and didn't make any substantial change, yes,
please carry the reviewed-by in your next iteration.
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:[~2025-12-03 7:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 17:40 [Buildroot] [PATCH] utils/generate-cyclonedx: fix monotonically increasing dependency list Nevo Hed via buildroot
2025-10-07 19:31 ` Nevo Hed via buildroot
2025-10-07 20:07 ` Thomas Perale via buildroot
2025-11-20 22:32 ` Thomas Petazzoni via buildroot
2025-12-02 21:34 ` Nevo Hed via buildroot
2025-12-03 7:46 ` Thomas Petazzoni via buildroot [this message]
[not found] ` <20251226041452.1040838-1-nhed+github@starry.com>
[not found] ` <20251226041452.1040838-2-nhed+github@starry.com>
2025-12-26 19:55 ` [Buildroot] [PATCH v2 1/1] " Nevo Hed via buildroot
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=20251203084614.3b7525c5@windsurf \
--to=buildroot@buildroot.org \
--cc=nhed+buildroot@starry.com \
--cc=thomas.perale@mind.be \
--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.