From: Quentin Schulz <quentin.schulz@cherry.de>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] doc: move licenses to doc/
Date: Tue, 14 Jan 2025 14:19:37 +0100 [thread overview]
Message-ID: <c57e066c-e3bf-4221-8dfd-9255f63c7b3f@cherry.de> (raw)
In-Reply-To: <20250101111920.18535-1-heinrich.schuchardt@canonical.com>
Hi Heinrich,
On 1/1/25 12:19 PM, Heinrich Schuchardt wrote:
> * Move all license texts to doc/
> * Convert README to restructured text and rename to index.rst
> * Replace '+' suffix by '-or-later' suffix
> * The eCos-2.0 license is OSI approved.
>
When one lists things done in a commit, it usually highlights those
should be separate commits, so please do have this split.
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> doc/develop/sending_patches.rst | 6 +-
> doc/index.rst | 1 +
> {Licenses => doc/licenses}/Exceptions | 0
I don't think this move is a good idea.
Reading this from the source code, I would believe those are licenses
applicable to the docs, not the whole source code.
Cheers,
Quentin
prev parent reply other threads:[~2025-01-14 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-01 11:19 [PATCH 1/1] doc: move licenses to doc/ Heinrich Schuchardt
2025-01-14 13:19 ` Quentin Schulz [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=c57e066c-e3bf-4221-8dfd-9255f63c7b3f@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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