unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: EmfoxZhou@gmail.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: ./make-dist for unicode branch
Date: Tue, 31 Jan 2006 10:08:25 +0900	[thread overview]
Message-ID: <E1F3k0P-0000gl-00@etlken> (raw)
In-Reply-To: <u3bj5ldti.fsf@gnu.org> (message from Eli Zaretskii on Mon, 30 Jan 2006 21:23:53 +0200)

In article <u3bj5ldti.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> How about if we check that all the generated source files that are not
> in the repository were regenerated?  (Excluding the *.elc, *.o, and
> other compiled files, of course.)  There shouldn't be too many, I
> think.

Perhaps.  But, I suggest to postpone the further discussion
on this matter because the problem is in emacs-unicode-2
branch only for the moment.  How about putting these entries
in TODO?

* Make the role of "./make-dist --snapshot" clear and, if
  necessary, fix make-dist to do that correctly.

* Decide how to handle admin/unidata/UnicodeData.txt and the
  generated files lisp/international/uni-*.el.

And, as this is administrative matter, that kind of TODO
file should be under "admin" subdir.

---
Kenichi Handa
handa@m17n.org

  reply	other threads:[~2006-01-31  1:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 15:43 ./make-dist for unicode branch Emfox Zhou
2006-01-17 19:56 ` Eli Zaretskii
2006-01-17 22:08   ` Emfox Zhou
2006-01-18  0:41     ` Kenichi Handa
2006-01-18  3:38       ` Emfox Zhou
2006-01-19 11:35         ` Kenichi Handa
2006-01-19 19:05           ` Emfox Zhou
2006-01-20  4:50             ` Kenichi Handa
2006-01-20  4:58               ` Miles Bader
2006-01-20  6:30                 ` Kenichi Handa
2006-01-20  6:56                   ` Miles Bader
2006-01-20 10:53                   ` Eli Zaretskii
2006-01-26  1:09                     ` Kenichi Handa
2006-01-26 17:46                       ` Richard M. Stallman
2006-01-26 21:21                         ` Eli Zaretskii
2006-01-27  0:49                           ` Kenichi Handa
2006-01-27  7:23                             ` Eli Zaretskii
2006-01-27  7:47                               ` Kenichi Handa
2006-01-28  4:50                                 ` Richard M. Stallman
2006-01-29 12:11                                   ` Kenichi Handa
2006-01-30  0:57                                     ` Richard M. Stallman
2006-01-30 12:32                                       ` Kenichi Handa
2006-01-30 19:23                                         ` Eli Zaretskii
2006-01-31  1:08                                           ` Kenichi Handa [this message]
2006-01-31  1:51                                         ` Miles Bader
2006-01-31 18:04                                         ` Richard M. Stallman
2006-01-27 22:32                           ` Richard M. Stallman
2006-01-20  6:13               ` Emfox Zhou
2006-01-20 10:11               ` Zhang Wei

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=E1F3k0P-0000gl-00@etlken \
    --to=handa@m17n.org \
    --cc=EmfoxZhou@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).