From: Andrew Cagney <ac131313@cygnus.com>
To: "David S. Miller" <davem@redhat.com>
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Sparc/Linux fixes part 1
Date: Sat, 20 Apr 2002 20:06:00 -0000 [thread overview]
Message-ID: <3CC22CA4.9060300@cygnus.com> (raw)
In-Reply-To: <20020420.185217.124826922.davem@redhat.com>
> From: "David S. Miller" <davem@redhat.com>
> Date: Fri, 19 Apr 2002 19:44:17 -0700 (PDT)
>
> I can't "look at the bfd and elf bits" to "find out" what the long
> double type size is. The information simply isn't there.
>
> Michael or someone, can we please bring closure to these
> issues? I've believe I've described my delimma ad nauseum
> at this point.
>
> Now, if debugging information contained the size/layout of
> fundamental C types, we could solve this using that. But
> I somehow doubt this information is provided that way.
I believe JasonT's drawn your attention to the ARM and, hence, you've
found a way to resolve this.
> On another topic, I have like 10 or so RFAs pending, and nobody
> provides any feedback. Yet someone else submits a patch after all of
> mine and it gets an RFA quite quickly. It's not like I'm submitting
> jumbo patches or anything, what gives?
>
> I want to maintain and fix up the Sparc port, but I cannot do that
> with multi-day lead times on patch review for even the most simple of
> changes. If nobody has the time to review my changes, then lets vote
> on letting me be the Sparc maintainer because I do have the time to
> keep it in good shape.
Unfortunatly, the changes you're making, while small, are often not
simple or obvious and, in the case of the patch that went with this
thread, not correct.
Please also appreciate that GDB runs on international time and most
everyone on this list has a day job. Your changes will be reviewed but
perhaphs not in the timeframe you seem to expect.
Andrew
next prev parent reply other threads:[~2002-04-21 3:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 14:54 David S. Miller
2002-04-19 18:37 ` Michael Snyder
2002-04-19 18:43 ` David S. Miller
2002-04-19 18:55 ` David S. Miller
2002-04-19 19:13 ` Andrew Cagney
2002-04-19 19:16 ` David S. Miller
2002-04-19 19:18 ` David S. Miller
2002-04-19 19:46 ` Andrew Cagney
2002-04-19 19:53 ` David S. Miller
2002-04-20 19:01 ` David S. Miller
2002-04-20 19:13 ` Jason R Thorpe
2002-04-20 19:44 ` Andrew Cagney
2002-04-20 20:06 ` Andrew Cagney [this message]
2002-04-20 20:18 ` David S. Miller
2002-04-20 21:24 ` Jason R Thorpe
2002-04-20 21:32 ` David S. Miller
2002-04-20 23:41 ` Andrew Cagney
2002-04-22 9:24 ` Elena Zannoni
2002-04-22 3:55 ` Richard Earnshaw
2002-04-22 4:09 ` David S. Miller
2002-04-19 19:55 ` David S. Miller
2002-04-20 10:00 ` Jason R Thorpe
2002-04-20 17:59 ` David S. Miller
2002-04-20 19:04 ` Jason R Thorpe
2002-04-20 19:19 ` David S. Miller
2002-04-20 19:24 ` Jason R Thorpe
2002-04-20 19:26 ` David S. Miller
2002-04-20 20:32 ` [RFA] Sparc OS abi gdbarch init (was Re: [RFA] Sparc/Linux fixes part 1) David S. Miller
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=3CC22CA4.9060300@cygnus.com \
--to=ac131313@cygnus.com \
--cc=davem@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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