all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: Assignment overview (again)
Date: Thu, 07 Jan 2016 00:16:32 +0000	[thread overview]
Message-ID: <871t9u5jmn.fsf@russet.org.uk> (raw)
In-Reply-To: <838u4jm1f9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Dec 2015 09:29:14 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Phillip Lord <phillip.lord@newcastle.ac.uk>
>> CC: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
>> Date: Thu, 24 Dec 2015 21:40:42 +0000
>> 
>> That is a reason why the full list cannot go up, not a reason why any list cannot go up.
>
> What do you mean by "any list"?  There are other private details
> there, how can we know who and why wouldn't want that to be public
> knowledge?

We ask them.

It's like the UK electoral register. There's the real one (i.e. who can
vote) and the public one (i.e. the subset of the real one that has not
withdrawn itself from the public one).

So, the FSF could ask at time of copyright assignment papers which
details people are happy with being public.

Phil



  reply	other threads:[~2016-01-07  0:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 19:31 Assignment overview (again) Lars Ingebrigtsen
2015-12-24 19:37 ` Lars Ingebrigtsen
2015-12-24 19:37 ` Eli Zaretskii
2015-12-24 19:41   ` Lars Ingebrigtsen
2015-12-24 19:50     ` Eli Zaretskii
2015-12-24 20:00       ` Lars Ingebrigtsen
2015-12-24 21:40   ` Phillip Lord
2015-12-25  7:29     ` Eli Zaretskii
2016-01-07  0:16       ` Phillip Lord [this message]
2016-01-07  3:40         ` Eli Zaretskii
2016-01-08  5:54           ` Richard Stallman
2016-01-08 13:48             ` Phillip Lord
2016-01-08 14:55               ` Jose E. Marchesi
2016-01-08 15:37               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871t9u5jmn.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.