From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: law question
Date: Sat, 22 May 2021 00:34:12 +0200 [thread overview]
Message-ID: <trinity-dfcca941-c8a3-43eb-8f18-779083d47f3b-1621636452386@3c-app-mailcom-bs04> (raw)
In-Reply-To: <871r9zdbqc.fsf@zoho.eu>
> Sent: Saturday, May 22, 2021 at 9:21 AM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Cc: emacs-devel@gnu.org
> Subject: Re: law question
>
> Christopher Dimech wrote:
>
> > We would need more details, e.g. the original release
> > license. If it is to be free software the implementation
> > went be different if the two licences are incompatible.
>
> Should we assume the worst-case scenario?
You could ask for a disclaimer of rights from said company. What license was
it released under?
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2021-05-21 22:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 20:59 law question Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:09 ` Jean Louis
2021-05-21 21:17 ` Christopher Dimech
2021-05-21 21:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:30 ` Jean Louis
2021-05-21 21:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:46 ` Christopher Dimech
2021-05-21 23:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 23:31 ` Christopher Dimech
2021-05-21 23:56 ` Christopher Dimech
2021-05-22 0:12 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 22:34 ` Christopher Dimech [this message]
2021-05-22 6:14 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-dfcca941-c8a3-43eb-8f18-779083d47f3b-1621636452386@3c-app-mailcom-bs04 \
--to=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).