From: Cœur <coeur@gmx.fr>
To: Leif Lindholm <leif.lindholm@linaro.org>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH] EmbeddedPkg: Fix various typos
Date: Thu, 04 Jul 2019 07:03:37 -0700 [thread overview]
Message-ID: <28803.1562249017634518697@groups.io> (raw)
In-Reply-To: <20190704130132.f56ssoz7d4womw2y@bivouac.eciton.net>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On Thu, Jul 4, 2019 at 09:01 PM, Leif Lindholm wrote:
>
> Urgh, don't make me elaborate on the implications of public domain
> versus copyright... If you're interested, have a look at
> https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
>
This link says:
> Some commonly used “Public Domain dedications” have already been included in the SPDX License List (e.g., ANTLR, Sax, CC-0).
And CC-0 was what I was proposing; I'm aware of the difference with American Public Domain, as, for the record, I'm an elected Wikipedia Administrator, so I've also had my share of licensing questions.
Anyway, BSD+Patent is really fine by me.
On Thu, Jul 4, 2019 at 09:01 PM, Leif Lindholm wrote:
>
> Out of interest - how did you find all these typos? I hope it was
> something at least semi-automated?
I think it was roughly two weeks of review with a spellchecker while being sick in bed. When I started, I never thought it would be so much time consuming. The only folders that I ignored were the AppPkg Python ones.
Thank you for the link to GMX Konfiguration, I'll try it for next patch.
Antoine
[-- Attachment #2: Type: text/html, Size: 1518 bytes --]
next prev parent reply other threads:[~2019-07-04 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 3:42 [PATCH] EmbeddedPkg: Fix various typos Cœur
2019-07-03 15:30 ` [edk2-devel] " Leif Lindholm
2019-07-03 16:58 ` Cœur
2019-07-04 13:01 ` Leif Lindholm
2019-07-04 14:03 ` Cœur [this message]
2019-07-04 14:20 ` Leif Lindholm
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-list 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=28803.1562249017634518697@groups.io \
--to=devel@edk2.groups.io \
/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