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: Fri, 21 May 2021 23:46:57 +0200 [thread overview]
Message-ID: <trinity-94da6ccc-541c-4d54-8556-cac72385a6fd-1621633617902@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?
Only if we cannot get all the required information to decide if we can use the code.
In principle, we should use all legal instruments at our disposal to use the code.
Have discussed with Richard that we customarily introduce cautionary attitudes
without good reason, which forces some to rewrite code for nothing.
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2021-05-21 21:46 UTC|newest]
Thread overview: 10+ 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:17 ` Christopher Dimech
2021-05-21 21:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-21 21:46 ` Christopher Dimech [this message]
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
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-94da6ccc-541c-4d54-8556-cac72385a6fd-1621633617902@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).