unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles.bader@necel.com>
Cc: EmfoxZhou@gmail.com, emacs-devel@gnu.org
Subject: Re: ./make-dist for unicode branch
Date: Fri, 20 Jan 2006 15:56:52 +0900	[thread overview]
Message-ID: <buolkxb5qvf.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <E1Ezpn7-00014D-00@etlken> (Kenichi Handa's message of "Fri, 20 Jan 2006 15:30:33 +0900")

Kenichi Handa <handa@m17n.org> writes:
>> If they're automatically generated, they shouldn't be in CVS...
>
> I basically agree with that.  But, then, how can we make
> them included in a tarball generated by Emfox's way?

I admit, I have no idea what the intended purpose of "--snapshot" is,
but for the normal case (no --snapshot), make-dist contains logic to
build any files that need to be generated (.elc files, info files, etc),
by calling "make" or invoking emacs or whatever.

It seems that this data should be handled in the same way.  Since
--snapshot results in "--no-update --no-check" it would seem to be imply
that it's up to the user to make sure their tree is in a sane state.

-Miles
-- 
We are all lying in the gutter, but some of us are looking at the stars.
-Oscar Wilde

  reply	other threads:[~2006-01-20  6:56 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 [this message]
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
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=buolkxb5qvf.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=EmfoxZhou@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).