From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: j12i <j+buildroot-list@maschinengott.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] Documentation patch with some small things that threw me off as a newcomer to the project.
Date: Tue, 4 Feb 2025 09:12:58 +0100 [thread overview]
Message-ID: <20250204091258.0e05dc7d@windsurf> (raw)
In-Reply-To: <20241122223158.5315-1-j+buildroot-list@maschinengott.de>
Hello,
On Fri, 22 Nov 2024 23:31:58 +0100
j12i <j+buildroot-list@maschinengott.de> wrote:
> From: j12i <j+buildroot@maschinengott.de>
>
> This is my first contribution to this project and at the same time my first time using git send-email. Please tell me if I'm doing it wrong, but don't get angry at me.
>
> This results from a conversation I had on IRC today with xogium.
>
> The change in docs/manual/getting.adoc is in reference to the following section in docs/manual/contribute.adoc:
>
> > Refer to Chapter 3, Getting Buildroot for more information on obtaining a Buildroot git tree.
Thanks a lot for your patch! Your proposed changes look sensible and
relevant. They may require a few tweaks when being applied, but overall
most likely they make sense.
However, in order for your patch to be applicable, we need:
- It to be sent with your real name
- It to have your Signed-off-by line
Could you check this and send a new iteration?
Thanks a lot!
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
prev parent reply other threads:[~2025-02-04 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 22:31 [Buildroot] [PATCH] Documentation patch with some small things that threw me off as a newcomer to the project j12i
2024-11-29 9:11 ` j+buildroot-list
2025-02-04 8:12 ` 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=20250204091258.0e05dc7d@windsurf \
--to=buildroot@buildroot.org \
--cc=j+buildroot-list@maschinengott.de \
--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