From: Randy Rude <randy.rude@gdcanada.com>
To: DJ Delorie <dj@redhat.com>
Cc: pbarada@mail.wm.sps.mot.com, peter@baradas.org,
kai.ruottu@luukku.com, gcc@gcc.gnu.org,
crossgcc@sources.redhat.com
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Date: Thu, 22 May 2003 14:59:00 -0000 [thread overview]
Message-ID: <1053615495.14605.37.camel@d1d6k111.bowman.gdcanada.com> (raw)
In-Reply-To: <200305211738.h4LHcjZ21775@greed.delorie.com>
On Wed, 2003-05-21 at 11:38, DJ Delorie wrote:
>
> > At least that way someone would have *seen* that its broken and
> > hopefully would've applied your patch(or created a better one).
>
> Someone did see the patch, and noted some problems with it. *I*
> didn't see the patch because the subject didn't catch my attention.
>
> http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00738.html
As noted, I made the bad assumption that submitting the patch would
bring attention to the problem (and the workaround patch solved my
immediate issue). I haven't had the opportunity to make the suggested
changes to the patch.
Oh well, should I now raise a PR on this (or did someone beat me to it)?
Randy
next prev parent reply other threads:[~2003-05-22 14:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 6:12 Peter Barada
2003-05-20 6:53 ` Erik Christiansen
2003-05-20 10:53 ` Kai Ruottu
2003-05-20 10:44 ` Kai Ruottu
2003-05-21 4:55 ` Peter Barada
2003-05-21 7:13 ` Peter Barada
2003-05-21 15:05 ` Randy Rude
2003-05-21 15:38 ` Peter Barada
2003-05-21 16:56 ` Randy Rude
2003-05-21 17:28 ` Joe Buck
2003-05-21 17:39 ` DJ Delorie
2003-05-22 14:59 ` Randy Rude [this message]
2003-05-22 17:36 ` DJ Delorie
2003-05-23 19:40 ` Randy Rude
2003-05-22 3:14 ` Peter Barada
2003-05-22 12:17 ` Kai Ruottu
2003-05-22 13:33 ` Peter Barada
2003-05-23 3:25 ` Peter Barada
2003-05-20 16:19 ` DJ Delorie
2003-05-20 21:06 ` Kaveh R. Ghazi
2003-05-20 21:44 ` DJ Delorie
2003-05-23 15:30 ` Kaveh R. Ghazi
2003-05-23 17:49 ` Joe Buck
2003-05-23 18:17 ` Peter Barada
2003-05-23 18:17 ` Joe Buck
2003-05-23 18:39 ` Peter Barada
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=1053615495.14605.37.camel@d1d6k111.bowman.gdcanada.com \
--to=randy.rude@gdcanada.com \
--cc=crossgcc@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kai.ruottu@luukku.com \
--cc=pbarada@mail.wm.sps.mot.com \
--cc=peter@baradas.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.
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).