From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Richard Stallman <rms@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
nicolas.rougier@inria.fr, emacs-devel@gnu.org
Subject: Re: [ELPA] New package: splash-screen
Date: Wed, 23 Sep 2020 22:14:07 -0400 [thread overview]
Message-ID: <jwvblhwq649.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1kLG7E-0001Ap-KL@fencepost.gnu.org> (Richard Stallman's message of "Wed, 23 Sep 2020 21:32:08 -0400")
> It is not "magical". It is information we want users to know,
> so we show it to them.
I fully agree with it when it comes to the product being under
a copyleft license, but I do not understand why we particularly want
people to know it is distributed with "absolutely no warranty".
AFAIK all the software I've ever seen came with "absolutely no
warranty". That applies to proprietary software just as much as
Free Software. So what do we have to gain by promoting this
"characteristic" of Emacs?
> Part of the reason we want them to know it is legal.
That's a part of the argument I do not understand and would like to
see developed.
> Part of it is to soread awareness of the FSF and the GNU GPL.
And what does "absolutely no warranty" have to do with the FSF and
the GPL?
Stefan
next prev parent reply other threads:[~2020-09-24 2:14 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 8:35 [ELPA] New package: splash-screen Nicolas P. Rougier
2020-09-20 11:24 ` Colin Baxter
2020-09-20 12:36 ` Nicolas P. Rougier
2020-09-20 13:34 ` Colin Baxter
2020-09-20 13:16 ` Stefan Monnier
2020-09-20 14:50 ` Nicolas P. Rougier
2020-09-20 17:50 ` Stefan Monnier
2020-09-20 20:33 ` Nicolas P. Rougier
2020-09-20 22:22 ` Stefan Monnier
2020-09-21 3:50 ` Richard Stallman
2020-09-21 5:47 ` Alfred M. Szmidt
2020-09-21 6:06 ` Nicolas P. Rougier
2020-09-21 11:09 ` Philip K.
2020-09-21 11:42 ` Nicolas P. Rougier
2020-09-21 15:24 ` Philip K.
2020-09-21 16:40 ` Philip K.
2020-09-21 17:22 ` Nicolas P. Rougier
2020-09-21 11:53 ` Alfred M. Szmidt
2020-09-21 12:29 ` Nicolas P. Rougier
2020-09-21 13:27 ` Stefan Monnier
2020-09-21 13:45 ` Thibaut Verron
2020-09-20 19:20 ` Juri Linkov
2020-09-20 20:53 ` Nicolas P. Rougier
2020-09-20 19:58 ` Lars Ingebrigtsen
2020-09-21 3:49 ` Richard Stallman
2020-09-22 12:59 ` Lars Ingebrigtsen
2020-09-23 3:42 ` Richard Stallman
2020-09-23 3:59 ` Stefan Monnier
2020-09-23 8:03 ` Mathias Dahl
2020-09-24 1:31 ` Richard Stallman
2020-09-24 6:17 ` Nicolas P. Rougier
2020-09-25 4:39 ` Richard Stallman
2020-09-23 12:36 ` Lars Ingebrigtsen
2020-09-23 16:21 ` Alfred M. Szmidt
2020-09-23 16:36 ` Nicolas P. Rougier
2020-09-24 1:32 ` Richard Stallman
2020-09-24 2:14 ` Stefan Monnier [this message]
2020-09-24 13:36 ` Lars Ingebrigtsen
2020-09-25 4:38 ` Richard Stallman
2020-09-25 10:04 ` Lars Ingebrigtsen
2020-09-25 11:26 ` Thibaut Verron
2020-09-26 4:37 ` Richard Stallman
2020-09-26 13:43 ` Lars Ingebrigtsen
2020-09-27 2:43 ` Richard Stallman
2020-09-27 8:54 ` Thibaut Verron
2020-09-27 9:42 ` Eli Zaretskii
2020-09-27 9:56 ` Thibaut Verron
2020-09-27 10:10 ` Eli Zaretskii
2020-09-27 10:34 ` Thibaut Verron
2020-09-27 10:50 ` Eli Zaretskii
2020-09-27 11:24 ` Thibaut Verron
2020-09-27 11:52 ` Lars Ingebrigtsen
2020-09-27 13:32 ` Jean Louis
2020-09-27 16:08 ` Stefan Monnier
2020-09-28 3:43 ` Richard Stallman
2020-09-28 11:56 ` Lars Ingebrigtsen
2020-09-28 14:02 ` Alfred M. Szmidt
2020-09-26 8:28 ` Dmitry Gutov
2020-09-26 9:45 ` Alfred M. Szmidt
2020-09-26 9:51 ` Eli Zaretskii
2020-09-26 14:34 ` Drew Adams
2020-09-27 2:45 ` Richard Stallman
2020-09-27 8:34 ` Dmitry Gutov
2020-09-27 8:52 ` Alfred M. Szmidt
2020-09-27 8:56 ` Thibaut Verron
2020-09-27 9:47 ` Eli Zaretskii
2020-09-27 10:03 ` Dmitry Gutov
2020-09-27 10:42 ` Nicolas P. Rougier
2020-09-27 14:03 ` Alfred M. Szmidt
2020-09-28 3:42 ` Richard Stallman
2020-09-28 6:29 ` Nicolas P. Rougier
2020-09-29 3:32 ` Richard Stallman
2020-09-27 14:23 ` Alfred M. Szmidt
2020-09-27 16:20 ` Stefan Monnier
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=jwvblhwq649.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=nicolas.rougier@inria.fr \
--cc=rms@gnu.org \
/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).