all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, EmfoxZhou@gmail.com
Subject: Re: ./make-dist for unicode branch
Date: Mon, 30 Jan 2006 21:23:53 +0200	[thread overview]
Message-ID: <u3bj5ldti.fsf@gnu.org> (raw)
In-Reply-To: <E1F3YCz-0002jV-00@etlken> (message from Kenichi Handa on Mon, 30 Jan 2006 21:32:37 +0900)

> From: Kenichi Handa <handa@m17n.org>
> CC: eliz@gnu.org, EmfoxZhou@gmail.com, emacs-devel@gnu.org
> Date: Mon, 30 Jan 2006 21:32:37 +0900
> 
> In article <E1F3NLx-0000H7-RS@fencepost.gnu.org>, "Richard M. Stallman" <rms@gnu.org> writes:
> 
> >> I think it is trivial.  Just check whether simple.elc exists.
> >     It doesn't assure that the bootstrap was really successful.
> 
> > Does that really matter here?
> 
> > The point is to detect the case where no bootstrap was done.  
> > It would be nice to detect the case of a failed bootstrap
> > also, but that is a different matter.  It is ok to detect
> > just the former.
> 
> 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?

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.

  reply	other threads:[~2006-01-30 19:23 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 [this message]
2006-01-31  1:08                                           ` Kenichi Handa
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u3bj5ldti.fsf@gnu.org \
    --to=eliz@gnu.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 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.