From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: "nmake info" Windows patch
Date: 22 Feb 2003 21:46:45 +0000 [thread overview]
Message-ID: <m2k7fs6la2.fsf@nyaumo.jasonr.f2s.com> (raw)
In-Reply-To: <7263-Sat22Feb2003211111+0200-eliz@is.elta.co.il>
"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> I don't mind if we require the Cygwin port of makeinfo (assuming it's
> okay with Jason, Andrew, and other developers who work on the Windows
> port of Emacs), but I think we should at least tell that clearly in
> the docs.
Requiring the cygwin port is not ideal, but it is better than not
having proper make rules to build the info files on Windows. Since
this only affects people who compile from CVS, we can live with this
until someone has time to make native ports of makeinfo work.
next prev parent reply other threads:[~2003-02-22 21:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 21:54 "nmake info" Windows patch Peter 'Luna' Runestig
2003-02-21 23:14 ` Peter 'Luna' Runestig
2003-02-22 9:21 ` Eli Zaretskii
2003-02-22 9:53 ` Peter 'Luna' Runestig
2003-02-22 11:40 ` Juanma Barranquero
2003-02-22 19:08 ` Eli Zaretskii
2003-05-20 9:08 ` Peter 'Luna' Runestig
2003-05-20 11:14 ` Jason Rumney
2003-05-20 13:10 ` Juanma Barranquero
2003-02-22 19:11 ` Eli Zaretskii
2003-02-22 21:46 ` Jason Rumney [this message]
2003-02-22 10:13 ` Jason Rumney
2003-02-22 19:11 ` Eli Zaretskii
2003-02-22 21:44 ` Jason Rumney
-- strict thread matches above, loose matches on Subject: below --
2003-08-15 16:04 Your Emacs changes Richard Stallman
2003-08-18 15:21 ` Peter 'Luna' Runestig
2003-08-19 7:51 ` Eli Zaretskii
2003-08-19 7:59 ` Peter 'Luna' Runestig
2003-08-19 17:46 ` Eli Zaretskii
2003-08-29 7:25 ` "nmake info" Windows patch (was: Your Emacs changes) Peter 'Luna' Runestig
2003-08-29 11:20 ` Eli Zaretskii
2003-08-29 11:35 ` "nmake info" Windows patch Peter 'Luna' Runestig
2003-08-29 15:11 ` Eli Zaretskii
2003-08-30 3:10 ` Richard Stallman
2003-05-20 11:28 Peter 'Luna' Runestig
2002-09-03 7:42 Peter 'Luna' Runestig
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=m2k7fs6la2.fsf@nyaumo.jasonr.f2s.com \
--to=jasonr@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 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.