unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
	Angelo Graziosi <angelo.graziosi@alice.it>,
	Eli Zaretskii <eliz@gnu.org>, "Richard M. Stallman" <rms@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Emacs 23.4 Updated Windows Binaries published
Date: Sun, 05 Feb 2012 22:26:38 -0800	[thread overview]
Message-ID: <4F2F729E.7090301@cs.ucla.edu> (raw)
In-Reply-To: <CANbX365LE16DwJKBJBDmrjs=iYwqWyt0ymFTxiEsawUjxHjRHQ@mail.gmail.com>

On 02/05/2012 09:42 PM, Lennart Borgman wrote:
> I can't see that this in a legal way prevents from pointing to sources
> that is not owned by the distributor.

The GPL is clear that one cannot satisfy its requirements merely by
pointing to sources that someone else happens to distribute.
If one distributes executables, then one also has the responsibility
to distribute sources, even if the sources are identical to someone
else's copy.

This topic came up last week with respect to a Mac port, and Richard
responded there the same way that I expect he'll respond here; please see
the thread starting at <http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10656#23>.



  reply	other threads:[~2012-02-06  6:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 16:34 Emacs 23.4 Updated Windows Binaries published Angelo Graziosi
2012-02-05 16:52 ` Eli Zaretskii
2012-02-05 17:12   ` Angelo Graziosi
2012-02-05 17:23     ` Juanma Barranquero
2012-02-06  5:09       ` Christoph Scholtes
2012-02-05 19:10   ` Lennart Borgman
2012-02-05 20:48     ` Eli Zaretskii
2012-02-05 21:24       ` Lennart Borgman
2012-02-06  4:01         ` Eli Zaretskii
2012-02-06  3:46     ` Stephen J. Turnbull
2012-02-06  4:15       ` Lennart Borgman
2012-02-06  5:22         ` Stephen J. Turnbull
2012-02-06  5:42           ` Lennart Borgman
2012-02-06  6:26             ` Paul Eggert [this message]
2012-02-06  7:12             ` Stephen J. Turnbull
2012-02-06  7:46               ` Stephen J. Turnbull
2012-02-06 13:49                 ` Lennart Borgman
2012-02-06 15:46                   ` Stephen J. Turnbull
2012-02-06 13:47               ` Lennart Borgman
2012-02-06 15:33                 ` Stephen J. Turnbull
2012-02-06 15:53                   ` Lennart Borgman
2012-02-06 17:01                     ` Stephen J. Turnbull
2012-02-06 21:40                       ` Lennart Borgman
2012-02-07  9:53                 ` Richard Stallman
2012-02-07 13:31                   ` Lennart Borgman
2012-02-07 15:57                   ` Paul Eggert
  -- strict thread matches above, loose matches on Subject: below --
2012-02-05  1:04 Christoph Scholtes

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=4F2F729E.7090301@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=rms@gnu.org \
    --cc=stephen@xemacs.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).