From: lolywk@tutanota.com
To: Aki <please@ignore.pl>
Subject: Re: [PATCH nt] Assume BSD 3-clause license
Date: Wed, 8 Oct 2025 09:49:48 +0200 (CEST) [thread overview]
Message-ID: <Ob1n2ZK--F-9@tutanota.com> (raw)
In-Reply-To: <5366e485-0a72-41d0-a053-1e30e5205dcc@ignore.pl>
I agree, my contributions are too small to take into account, the decision is all yours. But if you'd like my opinion, I'm fine with BSD 3-clause, thanks.
Oct 8, 2025, 14:35 by please@ignore.pl:
> On 08/10/2025 06:08, lolywk@tutanota.com wrote:
>
>> Hi Aki, i'm not sure if i had contributed to a software called nt before, i tried searching for the repo but couldn't find any.
>>
>> Could you please hand me the link to the repo so i could review it first?
>>
> Repo is at: https://git.ignore.pl/nt/
>
> A somewhat trimmed (it was double wrapped in mail headers) patch from your e-mail address is at: https://patches.ignore.pl/0000.html
>
> It's such a small change you may question my sanity, but, well, it's yours, or at least was sent from your address
>
prev parent reply other threads:[~2025-10-08 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 18:24 Aki
2025-10-08 4:08 ` lolywk
2025-10-08 7:35 ` Aki
2025-10-08 7:49 ` lolywk [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=Ob1n2ZK--F-9@tutanota.com \
--to=lolywk@tutanota.com \
--cc=please@ignore.pl \
/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