From: Miles Bader <miles@gnu.org>
Cc: eliz@gnu.org, EmfoxZhou@gmail.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: ./make-dist for unicode branch
Date: Tue, 31 Jan 2006 10:51:35 +0900 [thread overview]
Message-ID: <fc339e4a0601301751h1b946b73r@mail.gmail.com> (raw)
In-Reply-To: <E1F3YCz-0002jV-00@etlken>
2006/1/30, Kenichi Handa <handa@m17n.org>:
> I thought that the point was to prevent making an incomplete
> tarball. And, for that, it is necessary to detect the case
> where bootstrap failed. The merit of just checking if
> bootstrap was done or not regardless of the result is small,
> isn't it?
Why do you think that? I'd think by far the most common case would be
people who checked out but didn't build (i.e. the easy-to-detect
case).
Emacs does not attempt to do a rigorous up-to-date check anywhere
else, why should it do that here? That's especially true given the
low frequency of changes in unicode data files -- if the generated
files exist at all, they're probably good enough to use for a
snapshot.
-miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2006-01-31 1:51 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
2006-01-31 1:51 ` Miles Bader [this message]
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=fc339e4a0601301751h1b946b73r@mail.gmail.com \
--to=miles@gnu.org \
--cc=EmfoxZhou@gmail.com \
--cc=eliz@gnu.org \
--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).