From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: miles@gnu.org, emacs-devel@gnu.org
Subject: Re: config.in
Date: Wed, 17 Apr 2002 17:43:49 +0300 [thread overview]
Message-ID: <8123-Wed17Apr2002174348+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <m3zo028q32.fsf@Janik.cz> (Pavel@Janik.cz)
> From: Pavel@Janik.cz (Pavel =?iso-8859-2?q?Jan=EDk?=)
> Date: Wed, 17 Apr 2002 14:30:41 +0200
>
> My opinion is:
Let me give you feedback. Please don't take this as a rebuttal; I've
spoken my views, so you know what they are.
> - if users of CVS miss those files, I think it is much better to
> auto-generate daily snapshots of CVS for them
Snapshots are A Good Thing, but someone will have to volunteer to do
the job of either generating them manually or (preferably) automating
their generation on gnu.org machines. If no one volunteers, snapshots
will remain a pipe dream, and we cannot count on them to solve any
problems.
> - having autogenerated files is really important for (and before)
> release
> - when creating branch for a release, we will check files that
> got generated
>
> What do you think?
Issues that need IMHO to be addressed (until and unless there are
snapshots):
- what do we offer users of non-Posix platforms who use CVS?
- how do we make sure the versions of Autoconf and related tools
installed on the machines where the CVS version is built are
compatible between all the developers?
next prev parent reply other threads:[~2002-04-17 14:43 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 ` 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 ` Eli Zaretskii [this message]
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=8123-Wed17Apr2002174348+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--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).