From: Sean Sieger <sean.sieger@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: 23.1.95 pretest; windows binaries
Date: Mon, 05 Apr 2010 22:07:35 -0400 [thread overview]
Message-ID: <8763452v14.fsf@gmail.com> (raw)
In-Reply-To: 4BBA8253.4050502@gnu.org
The info files should have already been built in the source tarballs.
That's what I thought.
next prev parent reply other threads:[~2010-04-06 2:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 16:35 23.1.95 pretest; windows binaries Sean Sieger
2010-04-05 16:39 ` Drew Adams
2010-04-05 23:26 ` Christoph
2010-04-06 0:37 ` Jason Rumney
2010-04-06 2:07 ` Sean Sieger [this message]
2010-04-06 2:14 ` Christoph
2010-04-06 2:23 ` Sean Sieger
2010-04-06 5:06 ` Jason Rumney
2010-04-06 5:41 ` Drew Adams
2010-04-06 5:47 ` Drew Adams
2010-04-06 9:32 ` Jason Rumney
2010-04-06 11:28 ` Sean Sieger
2010-04-09 16:27 ` Sean Sieger
2010-04-07 3:20 ` Richard Stallman
2010-04-07 4:51 ` Christoph
2010-04-07 5:24 ` Eli Zaretskii
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=8763452v14.fsf@gmail.com \
--to=sean.sieger@gmail.com \
--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).