Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Davis <davikovs@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71
Date: Thu, 21 Dec 2023 08:42:52 +0100	[thread overview]
Message-ID: <20231221084252.287ba580@windsurf> (raw)
In-Reply-To: <CAHQn7pKn5-Ss+zVkEzGow6TNm8xc2kmfkWMEXe2zZbYmFOmQPw@mail.gmail.com>

Hello Davis,

On Thu, 21 Dec 2023 01:31:28 +0200
Davis <davikovs@gmail.com> wrote:

> Can somebody who understands the legal side better sign off this change?
> I sent the patch as discussed here
> https://lists.buildroot.org/pipermail/buildroot/2023-December/681118.html
> The patch itself (the few build configuration lines it adds) was
> created by me in my spare time and I submit it under Buildroot's
> license (GPL 2 or later).

Then, you are able to add your Signed-off-by at the end of your commit
message, and resubmit the patch, that's all what's needed.

Look at all other patches posted to the list, it will show you an
example of what the Signed-off-by line should look like.

There is also a great deal of information on how to submit patches to
Buildroot in our documentation at:
https://buildroot.org/downloads/manual/manual.html#submitting-patches

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

  reply	other threads:[~2023-12-21  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 18:32 [Buildroot] [PATCH 1/1] package/{bluez5_utils, bluez5_utils-headers}: bump to version 5.71 Davis Mosenkovs
2023-12-20 20:24 ` Thomas Petazzoni via buildroot
2023-12-20 23:31   ` Davis
2023-12-21  7:42     ` Thomas Petazzoni via buildroot [this message]
2023-12-21 22:41       ` Davis
2023-12-22  8:07         ` Thomas Petazzoni via buildroot
2023-12-22  8:33         ` Peter Korsgaard

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=20231221084252.287ba580@windsurf \
    --to=buildroot@buildroot.org \
    --cc=davikovs@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