From: cull@cock.li (Cull)
Subject: [9fans] Fw: Git/fs: Possibly Usable
Date: Wed, 3 Apr 2019 11:43:55 -0700 [thread overview]
Message-ID: <20190403184355.4628541.48324.188@cock.li> (raw)
In-Reply-To: <20190403184115.4628541.62303.186@cock.li>
>Sent: Wednesday, April 3, 2019 10:08 AM
>>On April 3, 2019 4:02:49 PM UTC, ori at eigenstate.org wrote:
>>Don't particularly care. At some point I'd like to commit it to 9front,
>>but I can relicense it then.
>>
>>Do you have a preference?
>?
>Probably MIT or a BSD.
>
>But I can also live with any copyleft of your choice.
Wouldn't BSD (2 clause) be the easiest to reliscence down the road?
next prev parent reply other threads:[~2019-04-03 18:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:02 [9fans] " ori
2019-04-03 16:59 ` Giacomo
2019-04-03 18:41 ` Cull
2019-04-03 18:43 ` Cull [this message]
2019-04-03 18:47 ` [9fans] Fw: " hiro
2019-04-03 19:24 ` Cull
2019-04-03 18:57 ` Kurt H Maier
2019-04-03 19:01 ` Cull
2019-04-03 19:02 ` [9fans] Fw: " Cull
2019-04-03 18:44 ` [9fans] " Ori Bernstein
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=20190403184355.4628541.48324.188@cock.li \
--to=cull@cock.li \
/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;
as well as URLs for NNTP newsgroup(s).