From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Obvious - compilation failure in proc-api.c
Date: Wed, 09 Mar 2005 23:41:00 -0000 [thread overview]
Message-ID: <20050309234126.GA5799@nevyn.them.org> (raw)
In-Reply-To: <1110411905.8084.34.camel@cpc2-oxfd5-5-0-cust103.oxfd.cable.ntl.com>
On Wed, Mar 09, 2005 at 11:45:05PM +0000, David Lecomber wrote:
> Dear all,
>
> It's been a while since I committed something, but here's one for the
> obvious fix rule. Someone prod me if I forgot to do something ;-)
>
> The old version failed to compile with Sun's Forte tools on Solaris 10
> for Opteron (and you should've seen the code formatting!)
What was the error? The style appears to be the same as the one Andrew
used all across GDB when he mass-converted.
(Yes, I think it's ugly.)
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-09 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 23:37 David Lecomber
2005-03-09 23:41 ` Daniel Jacobowitz [this message]
2005-03-10 0:02 ` David Lecomber
2005-03-10 1:01 ` Daniel Jacobowitz
2005-03-10 9:17 ` Mark Kettenis
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=20050309234126.GA5799@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@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