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: Fri, 22 Dec 2023 09:07:12 +0100	[thread overview]
Message-ID: <20231222090712.4ef84484@windsurf> (raw)
In-Reply-To: <CAHQn7pKD3HBJ96Pe90+gvsNehuALXGbXarqLDDcn8_M5hSKDrA@mail.gmail.com>

Hello Davis,

On Fri, 22 Dec 2023 00:41:23 +0200
Davis <davikovs@gmail.com> wrote:

> Just one more question, BlueZ itself is covered by a license that allows
> persons not affiliated with BlueZ or Buildroot to bump the package version,
> correct?

I don't even see how the license of a software could prevent that. And
"affiliated with BlueZ or Buildroot" has absolutely no legal meaning.

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-22  8:07 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
2023-12-21 22:41       ` Davis
2023-12-22  8:07         ` Thomas Petazzoni via buildroot [this message]
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=20231222090712.4ef84484@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