From: Romain Francoise <romain@orebokech.com>
To: mah@everybody.org (Mark A. Hershberger)
Cc: emacs-devel@gnu.org
Subject: Re: initial nxml merge
Date: Fri, 23 Nov 2007 19:27:32 +0100 [thread overview]
Message-ID: <87pry024x7.fsf@elegiac.orebokech.com> (raw)
In-Reply-To: <87k5o9h25c.fsf@everybody.org> (Mark A. Hershberger's message of "Fri, 23 Nov 2007 02:06:07 -0500")
mah@everybody.org (Mark A. Hershberger) writes:
> I have just merged a minimally tested nXML. I merged all the
> char-name/unicode/*.el files for now because, while this
> information is in the unicode branch, it isn't in HEAD. That
> still needs to be sorted out.
Thanks. A few integration notes:
* The nXML manual belongs in doc/misc, not in doc/emacs. You
probably want to adjust @setfilename to output the info file in
the info/ top-level directory, and enable compilation of the file
in the doc/misc Makefile.
* The NEWS file should not be in lisp/nxml, but in etc/. See
GNUS-NEWS, ERC-NEWS, etc. The README and TODO files can just be
removed, I think.
* The subdirs.el files should be generated, not committed in CVS.
next prev parent reply other threads:[~2007-11-23 18:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 7:06 initial nxml merge Mark A. Hershberger
2007-11-23 12:56 ` Vinicius Jose Latorre
2007-11-23 16:32 ` Mark A. Hershberger
2007-11-23 18:27 ` Romain Francoise [this message]
2007-11-23 18:59 ` Stefan Monnier
2007-11-23 19:40 ` Mark A. Hershberger
2007-11-23 19:59 ` David Kastrup
2007-11-23 20:00 ` Glenn Morris
2007-11-24 3:13 ` Richard Stallman
2007-11-24 15:25 ` David Kastrup
2007-11-25 3:42 ` Richard Stallman
2007-11-24 21:44 ` Dan Nicolaescu
2007-11-24 22:01 ` What happened to (defun x)? (was: initial nxml merge) David Kastrup
2007-11-24 22:48 ` What happened to (defun x)? martin rudalics
2007-11-24 22:51 ` David Kastrup
2007-11-24 23:11 ` martin rudalics
2007-11-24 23:06 ` Dan Nicolaescu
2007-11-24 23:44 ` Jay Belanger
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=87pry024x7.fsf@elegiac.orebokech.com \
--to=romain@orebokech.com \
--cc=emacs-devel@gnu.org \
--cc=mah@everybody.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).