From: Christoph Scholtes <cschol2112@googlemail.com>
To: Sean Sieger <sean.sieger@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-20110425 windows binaries
Date: Mon, 25 Apr 2011 06:31:57 -0600 [thread overview]
Message-ID: <4DB569BD.70901@gmail.com> (raw)
In-Reply-To: <87pqoa4j3g.fsf@gmail.com>
On 4/25/2011 6:21 AM, Sean Sieger wrote:
> The trunk was built and runs successfully on Windows. Binaries have
> been published in
>
> http://alpha.gnu.org/gnu/emacs/windows/
Sean,
were these built with GnuTLS support enabled?
Christoph
next prev parent reply other threads:[~2011-04-25 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 12:21 emacs-20110425 windows binaries Sean Sieger
2011-04-25 12:31 ` Christoph Scholtes [this message]
2011-04-25 12:35 ` Sean Sieger
2011-04-25 12:40 ` Ted Zlatanov
2011-04-25 12:49 ` Sean Sieger
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=4DB569BD.70901@gmail.com \
--to=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=sean.sieger@gmail.com \
/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).