public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@transmeta.com>
To: Ben Elliston <bje@redhat.com>
Cc: cgen@sources.redhat.com
Subject: Maintainer mode
Date: Fri, 08 Sep 2000 15:52:00 -0000	[thread overview]
Message-ID: <14777.28070.561930.767231@casey.transmeta.com> (raw)
In-Reply-To: <14777.27737.706634.552352@casey.transmeta.com>

Doug Evans writes:
 > Ben Elliston writes:
 >  > After thinking about it a bit, I am ready to propose that the opcodes
 >  > and sim Makefile.am's be modified so that they no longer rely on
 >  > `--enable-cgen-maint', but instead use the @MAINTAINER_MODE@
 >  > substitutions provided by AM_MAINTAINER_MODE to determine whether or
 >  > not to include rules for automatically regenerating files.
 >  > 
 >  > The advantages here are obvious: you need not remember an extra option
 >  > to `configure' and it works more obviously.
 > 
 > I recognize the reasons why one would want to do this.
 > I didn't do this because it carries extra burdens I wasn't prepared
 > to dump on binutils/gdb people.

Plus, turning on maintainer-mode often caused lots of trivial diffs
in lots of Makefile.in's/configure.in's (for me anyway).
When I'm hacking on cgen stuff, I'd rather just not be put the
the trouble of having to deal with all of that.  ymmv of course.

  reply	other threads:[~2000-09-08 15:52 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 [this message]
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

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=14777.28070.561930.767231@casey.transmeta.com \
    --to=dje@transmeta.com \
    --cc=bje@redhat.com \
    --cc=cgen@sources.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).