all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Fanael Linithien <fanael4@gmail.com>
To: "Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu>,
	emacs-devel@gnu.org
Cc: Richard Stallman <rms@gnu.org>
Subject: Re: Wish List: support making *scratch* persistent
Date: Wed, 4 Oct 2017 18:07:53 +0200	[thread overview]
Message-ID: <CA+o=1OUXfMa7MWBn+Ek4NZUBJrwyZJyn6OyBb2O-a0X2pvUxVg@mail.gmail.com> (raw)

2017-10-03 19:33 GMT+02:00 Jorge A. Alfaro-Murillo
<jorge.alfaro-murillo@yale.edu>:
> Richard Stallman writes:
>
>>   >   The "persistent-scratch" package available from MELPA does   >
>> exactly what you want.
>> Would someone like to organize getting legal papers for this package, so
>> we can include it in Emacs?
>
>
> It seems like Fanael Linithien is the sole author. I'm CC'ing them to know
> if they are interested.

Can you tell me what exactly do I gain from giving up the copyright to
the FSF? My code is free software[1] and I'd prefer it stayed that
way.

[1] That is, under a *sane* definition that precludes source dumps and
other development models not accessible to the general public (like
Emacs, where only the FSF can contribute) from being free software on
the basis that they merely conform to the letter, not the spirit;
being allowed to contribute upstream *is an important freedom* that
you lot conveniently omit in your definition.



             reply	other threads:[~2017-10-04 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 16:07 Fanael Linithien [this message]
2017-10-04 23:40 ` Wish List: support making *scratch* persistent Jean-Christophe Helary
  -- strict thread matches above, loose matches on Subject: below --
2017-10-02 11:01 Robert Inder
2017-10-02 13:32 ` Robert Weiner
2017-10-03 17:21   ` Richard Stallman
2017-10-03 17:33     ` Jorge A. Alfaro-Murillo

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='CA+o=1OUXfMa7MWBn+Ek4NZUBJrwyZJyn6OyBb2O-a0X2pvUxVg@mail.gmail.com' \
    --to=fanael4@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jorge.alfaro-murillo@yale.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.