From: Paul Barker <paul@pbarker.dev>
To: Sana Kazi <UpStream_IP-SK@bmwtechworks.in>,
openembedded-core@lists.openembedded.org
Cc: Sana Kazi <Kazi.S@bmwtechworks.in>
Subject: Re: [oe-core][master][PATCH] libgcrypt: Update license for dbg package
Date: Thu, 17 Sep 2026 08:52:52 +0100 [thread overview]
Message-ID: <5b8a0bd86988efd3ea73b38aa3e04a66a59d185a.camel@pbarker.dev> (raw)
In-Reply-To: <20260917063747.1037155-1-UpStream_IP-SK@bmwtechworks.in>
Hi,
On Thu, 2026-09-17 at 12:07 +0530, Sana Kazi wrote:
> From: Sana Kazi <Kazi.S@bmwtechworks.in>
>
> Set LICENSE for libgcrypt-dbg as "LGPL-2.1-or-later"
The commit message here says what you are changing, but not why. Please
include a brief explanation of why the -dbg package license is
different.
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-09-17 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 6:37 [oe-core][master][PATCH] libgcrypt: Update license for dbg package Sana Kazi
2026-09-17 7:11 ` Antonin Godard
2026-09-17 7:52 ` Paul Barker [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-17 8:06 Sana Kazi
2026-09-21 20:27 ` Richard Purdie
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=5b8a0bd86988efd3ea73b38aa3e04a66a59d185a.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=Kazi.S@bmwtechworks.in \
--cc=UpStream_IP-SK@bmwtechworks.in \
--cc=openembedded-core@lists.openembedded.org \
/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.