unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: The current rules for making Emacs binaries available on the net?
Date: Sat, 15 May 2010 00:51:51 +0200	[thread overview]
Message-ID: <AANLkTim9rrXRsXj3X17EHJRwnM1EYvMKzc5jUxRBMgH5@mail.gmail.com> (raw)
In-Reply-To: <E1OD22b-0008CL-MW@fencepost.gnu.org>

On Fri, May 14, 2010 at 11:03 PM, Richard Stallman <rms@gnu.org> wrote:
> See the GPL FAQ which is in gnu.org/licenses
> for GPL questions.

The section that is closes to my question seems to be this
(http://www.gnu.org/licenses/gpl-faq.html#UnchangedJustBinary):

   Can I put the binaries on my Internet server and put the
   source on a different Internet site?

      Yes. Section 6(d) allows this. However, you must
      provide clear instructions people can follow to obtain
      the source, and you must take care to make sure that
      the source remains available for as long as you
      distribute the object code.

Now if someone distributes unpatched binaries built from Emacs sources
is it then enough to tell from where this sources can be downloaded
and what revision number the checkout had?

My impression before was that this was not allowed, but looking at it
again I can not see why it should not be allowed.



  reply	other threads:[~2010-05-14 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 13:40 The current rules for making Emacs binaries available on the net? Lennart Borgman
2010-05-14 21:03 ` Richard Stallman
2010-05-14 22:51   ` Lennart Borgman [this message]
2010-05-15 20:27     ` Richard Stallman
2010-05-15 21:51     ` David Reitter
2010-05-16  6:38       ` Stephen J. Turnbull

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=AANLkTim9rrXRsXj3X17EHJRwnM1EYvMKzc5jUxRBMgH5@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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).