unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, angelo.graziosi@alice.it
Subject: Re: Emacs 23.4 Updated Windows Binaries published
Date: Sun, 5 Feb 2012 22:24:17 +0100	[thread overview]
Message-ID: <CANbX366JJAAsVFOHnQ9x537LevCycEJZQsjgPOPbiMCtyaYZHw@mail.gmail.com> (raw)
In-Reply-To: <837h01c8hn.fsf@gnu.org>

On Sun, Feb 5, 2012 at 21:48, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Lennart Borgman <lennart.borgman@gmail.com>
>> Date: Sun, 5 Feb 2012 20:10:50 +0100
>> Cc: Angelo Graziosi <angelo.graziosi@alice.it>, emacs-devel@gnu.org
>>
>> > That means unnecessary complications for the volunteers who produce
>> > the binaries, see the recent threads here (about GnuTLS, but not only
>> > about it).  For starters, we need to provide sources as well, and that
>> > might be tricky legal-wise.
>>
>> I have not been following this particular thread, but my understanding
>> is that only a link to the relevant sources is needed now - if we can
>> guarantee that this works. (This was my understanding of a message
>> from RMS quite some time ago. I might have misunderstood it, though.)
>
> You misunderstood.

If you think so then please explain to me what RMS meant here:

http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00430.html



  reply	other threads:[~2012-02-05 21:24 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 [this message]
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
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=CANbX366JJAAsVFOHnQ9x537LevCycEJZQsjgPOPbiMCtyaYZHw@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=angelo.graziosi@alice.it \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).