From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] docs/manual/contribute.adoc: mention license file changes in commit message
Date: Sat, 08 Aug 2026 15:47:59 +0200 [thread overview]
Message-ID: <292da31dfc09fec9ec31f9ca5419871c@free.fr> (raw)
In-Reply-To: <20260807202457.394955-1-fiona.klute@gmx.de>
On 07/08/2026 22:24, Fiona Klute via buildroot wrote:
> It has been good practice for a while to describe the kind of change
> in the commit message of any patch that changes license file
> hashes. This is important so any substantial changes don't go
> unnoticed. However it wasn't explicitly stated in the manual, fix
> that.
>
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-08 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 20:24 [Buildroot] [PATCH 1/1] docs/manual/contribute.adoc: mention license file changes in commit message Fiona Klute via buildroot
2026-08-08 13:47 ` 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=292da31dfc09fec9ec31f9ca5419871c@free.fr \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=ju.o@free.fr \
/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