public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: Lincoln Peters <sampln@sbcglobal.net>, xconq7@sources.redhat.com
Subject: Re: Bug in acp-independent action code
Date: Tue, 15 Jun 2004 05:19:00 -0000	[thread overview]
Message-ID: <1087276555.17707.35.camel@localhost.localdomain> (raw)
In-Reply-To: <l03130300bcf3d6542426@[212.181.162.155]>

On Mon, 2004-06-14 at 17:31, Hans Ronne wrote:

> 2. Another fix would be to move part of the acp-independent build code into
> do_build_action, so that materials are consumed only when the action is
> executed (i.e. after check_build_action).
> This would make sense, and is something I have planned to do. However, it
> is not a trivial thing to do since the acp-independent build code differs a
> lot from the normal build code.

I certainly favor this option the most. The more common/unified code
that we can make, the easier it is to maintain/fix/expand.

Eric

      parent reply	other threads:[~2004-06-15  5:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11  6:17 Lincoln Peters
2004-06-11  6:40 ` Hans Ronne
2004-06-12  6:45   ` Lincoln Peters
2004-06-12  9:01     ` Hans Ronne
2004-06-13 21:45     ` Hans Ronne
2004-06-14 23:34     ` Hans Ronne
2004-06-15  4:55       ` Lincoln Peters
2004-06-15  7:18         ` Hans Ronne
2004-06-15 20:51           ` Lincoln Peters
2004-06-16  4:08             ` New Wreck-Type Options Elijah Meeks
2004-06-16 13:49               ` Eric McDonald
2004-06-16 21:00             ` Bug in acp-independent action code Hans Ronne
2004-06-15  5:19       ` Eric McDonald [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=1087276555.17707.35.camel@localhost.localdomain \
    --to=mcdonald@phy.cmich.edu \
    --cc=hronne@comhem.se \
    --cc=sampln@sbcglobal.net \
    --cc=xconq7@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).