From: Colin Walters <walters@debian.org>
Subject: Re: config.in
Date: 17 Apr 2002 00:59:02 -0400 [thread overview]
Message-ID: <1019019542.3342.132.camel@space-ghost> (raw)
In-Reply-To: <4009-Wed17Apr2002074417+0300-eliz@is.elta.co.il>
[ No need to CC me ]
On Wed, 2002-04-17 at 00:44, Eli Zaretskii wrote:
> > From: ams@kemisten.nu (Alfred M. Szmidt)
> > Date: 16 Apr 2002 23:21:24 +0200
> >
> > Should users use the CVS version of Emacs?
>
> We have anon CVS so they could. Quite a few do.
As Miles said, those users are not the normal user; the CVS tree should
be intended for developers. If we have a large number of "normal users"
using the CVS tree as their daily working environment, then this seems
to me to suggest that there is something wrong with our release process.
Incidentally, I'm working on tracking down authorship of the autogen.sh
included in the GNOME CVS repository; it wouldn't be hard to write our
own, but it would be good to reuse the already existing code.
next prev parent reply other threads:[~2002-04-17 4:59 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 ` Colin Walters [this message]
2002-04-17 5:08 ` config.in Miles Bader
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
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=1019019542.3342.132.camel@space-ghost \
--to=walters@debian.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).