Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Denis Joseph Barrow <DJBARROW@de.ibm.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: New gdb 31 & 64 bit patches for S/390
Date: Wed, 15 Aug 2001 09:54:00 -0000	[thread overview]
Message-ID: <3B7AA7D9.90005@cygnus.com> (raw)
In-Reply-To: <OF52CDD1AF.3BB91388-ONC1256AA9.003124BC@de.ibm.com>

> If anything the code quality may be deteriorating owing to being asked to
> move code around so much & possibly being tired of retesting it,
> I currently have 4 versions of the code to support the post 5.0 32 & 64 bit
> patches the 5.0 32 & 64 bit patches & a lot of other work to do
> besides & probably falling back on it, when enthuasism is low my
> productivity deteriorates badly, this crap is pissing me off.
>  I will remove the non multi arch definitions when I don't have to support
> gdb-5.0.

That is your decision.

As things stand, the FSF doesn't own this code and, as a consequence, 
people have strong reservations about working on it.  (IBM will only 
assign the copyright using a letter that cites a digitally signed patch. 
  I understand this process to be slow and complicated.).

This is unfortunate.  As you'll recall, I have, on several occasions, 
suggested that instead of trying to get the source code up-to-scratch, 
it instead be assigned as-is to the FSF.  That way, others (probably me) 
would have been able to more directly help with the task of merging the 
changes in.

Instead, as you note, we've ended up with a slow painful process where 
the code would be submited and then I would eventually (since no one 
else step forward :-) review it.

Could I again suggest that the patches be assigned, as-is, to the FSF.

> We did our first 31 bit gdb drop 20 months ago.
> Even redhat has a experimental 64 bit drop for the last 6 months & it still
> isn't gnu.org the repository .

Yes, isn't this ironic.  I won't go near (and Red Hat can't contribute) 
those changes either since they are also legally owned by IBM :-)

	Andrew



  parent reply	other threads:[~2001-08-15  9:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-15  2:22 Denis Joseph Barrow
2001-08-15  9:03 ` Andrew Cagney
2001-08-15  9:54 ` Andrew Cagney [this message]
     [not found] <OFEFF0AD94.761C34C1-ONC1256AB6.005503EE@de.ibm.com>
2001-08-28 16:33 ` Daniel Jacobowitz
2001-09-05 21:45   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13  9:47 Denis Joseph Barrow
2001-08-13  3:06 Denis Joseph Barrow
2001-08-13  9:31 ` Andrew Cagney
2001-07-06  2:31 Denis Joseph Barrow
2001-07-05 10:24 Denis Joseph Barrow
2001-07-05 12:46 ` Andrew Cagney
2001-07-08  0:53   ` Eli Zaretskii
2001-07-08 19:23     ` Andrew Cagney
2001-07-05  9:19 Denis Joseph Barrow
2001-07-05 12:36 ` Andrew Cagney
2001-07-05  9:15 Denis Joseph Barrow
2001-07-05  5:04 Denis Joseph Barrow
2001-07-05  3:57 Denis Joseph Barrow
2001-07-05 10:11 ` Andrew Cagney
2001-07-05 10:11 ` Andrew Cagney
2001-07-05  3:12 Denis Joseph Barrow
2001-06-18  3:32 DJBARROW
     [not found] <C1256A02.00573066.00@d12mta09.de.ibm.com>
2001-03-01 10:39 ` Nick Clifton
2001-03-01  2:50 DJBARROW
2001-03-01 10:37 ` Nick Clifton
2001-02-27 12:39 DJBARROW
2001-02-28 16:13 ` Nick Clifton
2001-06-15  9:53 ` Andrew Cagney
2001-06-15 11:46   ` Andreas Jaeger
2001-06-15 12:22     ` Andrew Cagney
2001-07-04 11:25 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney
2001-07-04 21:02 ` Andrew Cagney

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=3B7AA7D9.90005@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=DJBARROW@de.ibm.com \
    --cc=gdb-patches@sourceware.cygnus.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