From: Eric Christopher <echristo@cygnus.com>
To: Ben Elliston <bje@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, cgen@sources.redhat.com
Subject: Re: Maintainer mode
Date: Sat, 09 Sep 2000 02:00:00 -0000 [thread overview]
Message-ID: <39B9FE3D.9B063E5B@cygnus.com> (raw)
In-Reply-To: <14777.45755.343763.449957@walkabout.cygnus.com>
>
> Now that I've had time to think about this one, the idea of
> eliminating --enable-cgen-maint and removing generated files are
> independent. I am happy with your suggestion to leave the generated
> files there--this is what happens now with `configure.in' and
> `configure', for instance.
>
What we did in gcc is remove some of the generated files from cvs, but
leave them in the snapshots. The idea is that someone working on the
compiler (cvs) should have all of the tools to work on the compiler, but
that the generated files should be there for the casual user.
-eric
prev parent reply other threads:[~2000-09-09 2:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-08 15:35 Ben Elliston
2000-09-08 15:47 ` Doug Evans
2000-09-08 15:52 ` Doug Evans
2000-09-09 1:48 ` Ben Elliston
2000-09-09 12:21 ` Doug Evans
[not found] ` <20000908184128.B29784@redhat.com>
2000-09-09 1:48 ` Ben Elliston
2000-09-09 2:00 ` Eric Christopher [this message]
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=39B9FE3D.9B063E5B@cygnus.com \
--to=echristo@cygnus.com \
--cc=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=fche@redhat.com \
/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.
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).