From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com,
Andrew Cagney <ac131313@cygnus.com>,
"David S. Miller" <davem@redhat.com>,
shebs@apple.com
Subject: Re: which patches to review
Date: Thu, 25 Apr 2002 18:45:00 -0000 [thread overview]
Message-ID: <20020425214551.A12948@nevyn.them.org> (raw)
In-Reply-To: <20020426013611.GA30067@redhat.com>
On Thu, Apr 25, 2002 at 09:36:11PM -0400, Christopher Faylor wrote:
> On Thu, Apr 25, 2002 at 09:13:24PM -0400, Daniel Jacobowitz wrote:
> >On Thu, Apr 25, 2002 at 10:32:29AM -0400, Andrew Cagney wrote:
> >> > From: Andrew Cagney <ac131313@cygnus.com>
> >> >Date: Wed, 24 Apr 2002 13:15:57 -0400
> >> >
> >> > Here, you're mistaken.
> >> >
> >> >He isn't %100 wrong. I've been asked repeatedly to basically
> >> >multi-arch the Sparc targets out the wazoo to get the Linux
> >> >Sparc bits in.
> >>
> >> One of GDB's overriding objectives it to get everything multi-arch. To
> >> that end:
> >>
> >> Post 5.0, every new architecture has to be mult-arched
> >> Post 5.1, every addition to an existing architecture has to be mult-arch
> >> enabled
> >>
> >> As acceptence criteria, they are simple and transparent. I don't think
> >> me stiching up some sort of cosy deal where you were some how excempted
> >> from this would go down very well :-)
> >
> >Again with due respect, I've got to object to the point of view in this
> >message. I wouldn't say that becoming multi-arch is "one of GDB's
> >overriding objectives". It's something that we all agree would be good
> >for GDB; it's something that I agree with you should happen before our
> >next release, which is not scheduled for at least four months IIRC.
> >But if it is an "overriding objective", it's only so for you. My
> >overriding objective is for GDB to improve.
>
> Hmm. I was under the impression that 1) Andrew was the head maintainer
> for gdb
If so, this isn't said anywhere. It certainly may be true; all I know
is that he's a blanket write maintainer and the release manager for the
last several releases. If the GDB projects has a single head
maintainer, perhaps that should be listed in gdb/MAINTAINERS somewhere?
> and, so, got to specify little things like "overriding
> directions" for gdb, and
To the extent of excluding large contributions that don't seem to
conflict in any substantial way with his design improvements?
> 2) multiarching targets was an improvement.
Sure it is. So are David's SPARC/Linux patches, and they're a much
more concrete one to users. I was just objecting to the one
"obviously" trumping with the other.
I'm going to shut up now; I've no desire for a protacted argument and
I've foolishly walked into the middle of one.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-26 1:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:49 David S. Miller
2002-04-23 7:47 ` Elena Zannoni
2002-04-23 7:54 ` Daniel Jacobowitz
2002-04-23 22:19 ` David S. Miller
2002-04-24 8:53 ` Stan Shebs
2002-04-24 10:16 ` Andrew Cagney
2002-04-24 10:48 ` David S. Miller
2002-04-24 12:16 ` Kevin Buettner
2002-04-24 12:25 ` David S. Miller
2002-04-25 7:04 ` Andrew Cagney
[not found] ` <mailpost.1019743470.13502@news-sj1-1>
2002-04-25 9:19 ` cgd
2002-04-25 7:32 ` Andrew Cagney
2002-04-25 18:04 ` David S. Miller
2002-04-25 20:27 ` Andrew Cagney
2002-04-25 18:14 ` Daniel Jacobowitz
2002-04-25 18:36 ` Christopher Faylor
2002-04-25 18:45 ` Daniel Jacobowitz [this message]
2002-04-25 19:17 ` Christopher Faylor
2002-04-25 20:33 ` Andrew Cagney
2002-04-26 9:26 ` Stan Shebs
2002-04-25 20:17 ` Andrew Cagney
2002-04-25 22:00 ` Daniel Jacobowitz
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=20020425214551.A12948@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=davem@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=shebs@apple.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