all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Assignment for GNUS vs. EMACS
Date: Mon, 05 Mar 2007 00:22:44 +0100	[thread overview]
Message-ID: <85649gmw57.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3slck8vgr.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Mon\, 05 Mar 2007 00\:01\:08 +0100")

storm@cua.dk (Kim F. Storm) writes:

> In the assignments file, we have separate assignments for GNUS and
> EMACS.  But since GNUS is included with EMACS these days, does an
> assignment for EMACS cover changes to GNUS too?

If one wanted to be really anal about it, the assignment expresses the
intent of the contributor about _what_ code contributions should be
unambiguously considered the property of the FSF, not _where_ they may
end up.

With that interpretation, a contribution made to the Emacs CVS would
have been cleared as being the property of the FSF (from whence it may
be propagated into GNUS with that ownership), whereas a contribution
made to the GNUS CVS would not appear declared as transferred to the
FSF (and would not become so even if somebody else took it and
propagated it back into Emacs).

I am not sure that even the FSF's lawyers are as paranoid as that,
though.  But since some might delight in that level of nitpicking, I
decided to contribute it nevertheless.

In any case, it should be safe if one just checks into CVS servers of
those projects for which one has an assignment.

> OTOH, I guess that an assigment for GNUS doesn't cover EMACS in general.

Yup, that too.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-03-04 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 23:01 Assignment for GNUS vs. EMACS Kim F. Storm
2007-03-04 23:22 ` David Kastrup [this message]
2007-03-05 15:25 ` Richard Stallman

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=85649gmw57.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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.