From: Eric Christopher <echristo@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
"Mark Williams (MWP)" <mwp@internode.on.net>,
gcc@gcc.gnu.org, DJ Delorie <dj@redhat.com>
Subject: Re: Error building 4.0.1-RC2
Date: Thu, 23 Jun 2005 01:09:00 -0000 [thread overview]
Message-ID: <1119487997.3325.3.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <42B9704C.2020306@codesourcery.com>
On Wed, 2005-06-22 at 07:06 -0700, Mark Mitchell wrote:
> Eric Christopher wrote:
> >>
> >>If someone wishes to submit a patch for that bug for 4.0 branch, I expect
> >>it could be considered for 4.0.2 but might be too risky for 4.0.1 now.
> >>
> >
> >
> > Like so? Tested by building outside the source directory and attempting
> > to build in the source directory. Did we want something like this for
> > mainline too?
>
> This is OK, even for 4.0.1. It's also OK for mainline, and for 4.0.2,
> if you don't get it checked in before 4.0.1.
Checked it in today. Apparently mainline does this correctly right now,
though unless we plan on supporting it in the future an AC_MSG_WARN
might be good. "This may not work"
-eric
next prev parent reply other threads:[~2005-06-23 1:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 5:46 Mark Williams (MWP)
2005-06-20 5:50 ` Eric Christopher
2005-06-20 6:12 ` Mark Williams (MWP)
2005-06-20 10:56 ` Joseph S. Myers
2005-06-21 22:17 ` Eric Christopher
2005-06-21 22:24 ` DJ Delorie
2005-06-21 22:31 ` Eric Christopher
2005-06-21 22:44 ` Eric Christopher
2005-06-21 22:46 ` DJ Delorie
2005-06-22 14:06 ` Mark Mitchell
2005-06-23 1:09 ` Eric Christopher [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-20 5:32 Mark Williams (MWP)
2005-06-20 5:41 ` Eric Christopher
2005-06-20 6:30 ` Ranjit Mathew
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=1119487997.3325.3.camel@dzur.sfbay.redhat.com \
--to=echristo@redhat.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=mark@codesourcery.com \
--cc=mwp@internode.on.net \
/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).