This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: New s390 gdb patch





>GDB no longer accepts new targets that do not use the new multi-arch
>framework.  See the m68hc11 target.


I was going for a re check in today until I saw this bloody bomb #$%^%!!!

D.J. Barrow Linux for S/390 kernel developer
eMail: djbarrow@de.ibm.com,barrow_dj@yahoo.com
Phone: +49-(0)7031-16-2583
IBM Germany Lab, Schönaicherstr. 220, 71032 Böblingen


Andrew Cagney <ac131313@cygnus.com> on 29.09.2000 02:44:14

Please respond to Andrew Cagney <ac131313@cygnus.com>

To:   Denis Joseph Barrow/Germany/Contr/IBM@IBMDE
cc:   Boas Betzler/Germany/IBM@IBMDE, Gregory Burke/Poughkeepsie/IBM@IBMUS,
      gdb-patches@sourceware.cygnus.com, Michael Snyder
      <msnyder@redhat.com>, Martin Schwidefsky/Germany/IBM@IBMDE, Binutils
      Patches <binutils@sourceware.cygnus.com>
Subject:  Re: New s390 gdb patch




I'd suggest having a look through the files src/MAINTAINERS and
src/gdb/CONTRIBUTE.

The patches to */bfd need to be sent to binutils@sources.redhat.com for
approval.  I'm not the binutils maintainer.

The patch to config.sub need to be submitted to the config maintainer.
Contact details are on http://www.gnu.org.

The patch contains ChangeLog entries as a diff.  Please do not do that,
please separate out those entries and please format them consitent with
other ChangeLog entries.

The change to gdb/config.in replaces one test for link_map32 with
another different test.  It needs to be written in a way such that both
the old and the new test work.

The changes to opcodes/* need to be sent to the binutils mailing list
for approval.

The changes to readline/* need to be sent to the readline maintainer.
Only once approved there will I accept them.

GDB no longer accepts new contributions that contain PARAMS or K&R c.

GDB no longer accepts new targets that do not use the new multi-arch
framework.  See the m68hc11 target.

Many of the C files don't comply with the gnu coding standard.  I'd
suggest running the code through GNU indent.

The copyright notices will need to be updated :-)

--

Rather than let this dangle, and given the legal hoops it sounds like
you are going through, I'd like to propose that a branch be created and
your patches, as submitted, be applied to that.  It will then be
possible to work through all the issues and get the changes merged into
trunk.

If this was done, would it be reasonable to assume that your assignment
would allow you to submit changes (without further legal hoops) to the
public repository.  (Better ask that lawyer?)

The alternative, unfortunatly, is to break down the patches into BFD and
GDB parts, resolve each of the issues, and then submit the patches and
paper work.

     again sorry,
          Andrew


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]