From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: help-emacs-windows@gnu.org
Subject: Re: [h-e-w] emacs-20110510 windows binaries
Date: Thu, 12 May 2011 13:59:15 -0500 [thread overview]
Message-ID: <877h9vzqws.fsf@lifelogs.com> (raw)
In-Reply-To: BANLkTin8GJdN0a6GSnX9CV=QU5dWZwLdUA@mail.gmail.com
On Thu, 12 May 2011 20:47:17 +0200 Juanma Barranquero <lekktu@gmail.com> wrote:
JB> 2011/5/12 Ted Zlatanov <tzz@lifelogs.com>:
>> I am not sure we want to rely on a personal web site for distributing
>> Emacs-related security code. Maybe Sean or someone else should copy or
>> compile and then host those DLLs, ideally together with the Emacs binary
>> distribution.
JB> That's for the maintainers to decide.
I'm not sure which maintainers you mean. The Emacs maintainers? Do
they care? The distribution maintainer (Sean in this case) seems like
the more important decision maker.
JB> And, IIUC, distributing the binary DLLs means making also the code
JB> accesible, doesn't it?
The GnuTLS code is accessible at git://git.savannah.gnu.org/gnutls.git
It doesn't have to be distributed with the binaries IIUC, but a link to
the source code should be provided.
Ted
next prev parent reply other threads:[~2011-05-12 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 18:10 emacs-20110510 windows binaries Sean Sieger
2011-05-12 13:03 ` Ted Zlatanov
2011-05-12 13:41 ` Juanma Barranquero
2011-05-12 14:39 ` Ted Zlatanov
2011-05-12 15:01 ` [h-e-w] " Juanma Barranquero
2011-05-12 17:03 ` Ted Zlatanov
2011-05-12 18:47 ` Juanma Barranquero
2011-05-12 18:59 ` Ted Zlatanov [this message]
2011-05-12 19:29 ` Juanma Barranquero
2011-05-13 6:04 ` Eli Zaretskii
2011-05-13 14:50 ` Ted Zlatanov
2011-05-13 16:25 ` Sean Sieger
2011-05-12 19:27 ` Drew Adams
2011-05-12 19:33 ` Ted Zlatanov
2011-05-12 16:51 ` Sean Sieger
2011-05-13 2:18 ` Christoph Scholtes
2011-05-13 10:51 ` Juanma Barranquero
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=877h9vzqws.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@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 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.