all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: ams@kemisten.nu, walters@verbum.org, emacs-devel@gnu.org
Subject: Re: config.in
Date: 17 Apr 2002 14:08:19 +0900	[thread overview]
Message-ID: <buoads2ap4s.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <4009-Wed17Apr2002074417+0300-eliz@is.elta.co.il>

"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > Should users use the CVS version of Emacs?
> 
> We have anon CVS so they could.  Quite a few do.

But those that do quite definitely fall into the class of `unusually
clueful users', even if they don't write any code.  Such people are
quite competent to install the auto* tools; it's not rocket science.

In any case, the _purpose_ of the CVS repository is for development;
it's nice that `clueful' users can also use it to get the latest
sources, but that's a secondary purposes.  The proper thing to do is to
optimize the situation fo _developers_, even if it means a slight extra
inconvenience for this special class of users.

In any case (as I noted before) due to the the timestamp problem, `mere
users' that use CVS are going to end up needing the auto* tools anyway,
even if they never modify a single file, _even if_ the auto-generated
files are in CVS.

-Miles
-- 
Love is a snowmobile racing across the tundra.  Suddenly it flips over,
pinning you underneath.  At night the ice weasels come.  --Nietzsche

  parent reply	other threads:[~2002-04-17  5:08 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 18:24 config.in Eli Zaretskii
2002-04-16 18:45 ` config.in Miles Bader
2002-04-16 19:40   ` config.in Colin Walters
2002-04-16 21:00     ` config.in Eli Zaretskii
2002-04-16 21:21       ` config.in Alfred M. Szmidt
2002-04-17  4:44         ` config.in Eli Zaretskii
2002-04-17  4:59           ` config.in Colin Walters
2002-04-17  5:08           ` Miles Bader [this message]
2002-04-17  9:29             ` config.in Andreas Schwab
2002-04-17  0:00       ` config.in Karl Eichwalder
2002-04-17  5:13         ` config.in Eli Zaretskii
2002-04-17  9:24           ` config.in Andreas Schwab
2002-04-17  1:08       ` config.in Miles Bader
2002-04-17  5:33         ` config.in Eli Zaretskii
2002-04-17  5:54           ` config.in Miles Bader
2002-04-17  9:22             ` config.in Eli Zaretskii
2002-04-17  9:28             ` config.in Andreas Schwab
2002-04-17 12:09               ` config.in Miles Bader
2002-04-18 18:45         ` config.in Richard Stallman
2002-04-19 10:08           ` config.in Andreas Schwab
2002-04-19 12:19             ` config.in Kim F. Storm
2002-04-19 11:42               ` config.in Andreas Schwab
2002-04-19 13:02                 ` config.in Kim F. Storm
2002-04-20 17:26             ` config.in Richard Stallman
2002-04-21 15:58               ` config.in Andreas Schwab
2002-04-22  7:47                 ` config.in Richard Stallman
2002-04-22  9:18                   ` config.in Andreas Schwab
2002-04-23  0:24                     ` config.in Richard Stallman
2002-04-23  9:54                       ` config.in Andreas Schwab
2002-04-24 17:55                         ` config.in Richard Stallman
2002-04-24 18:27                           ` config.in Andreas Schwab
2002-04-26  3:17                             ` config.in Richard Stallman
2002-04-26 14:32                               ` config.in Andreas Schwab
2002-04-26 14:05                             ` config.in Kim F. Storm
2002-04-27 22:41                               ` config.in Richard Stallman
2002-04-17 12:30   ` config.in Pavel Janík
2002-04-17 14:43     ` config.in Eli Zaretskii
2002-04-17 19:34       ` config.in Pavel Janík
2002-04-18 18:45     ` config.in Richard Stallman
2002-04-17 16:05   ` config.in Richard Stallman
2002-04-17 17:13     ` config.in Eli Zaretskii
2002-04-17 17:40       ` config.in Colin Walters
2002-04-17 19:30         ` config.in Pavel Janík

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=buoads2ap4s.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=ams@kemisten.nu \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=walters@verbum.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.