Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: scottb@corelcomputer.com
Cc: gdb-patches@cygnus.com
Subject: Re: Contributing code...
Date: Thu, 24 Dec 1998 14:54:00 -0000	[thread overview]
Message-ID: <199812242254.OAA07707@andros.cygnus.com> (raw)
In-Reply-To: <36788854.77103CD8@corelcomputer.com>

   Date: Wed, 16 Dec 1998 23:28:04 -0500
   From: "Scott Bambrough" <scottb@corelcomputer.com>

   My name is Scott Bambrough.  I work for Corel Computer, a division of Corel
   Corporation that manufactures a small computer based on the DEC (now Intel)
   SA110 processor.  Several  months ago, working with a some clever folks in
   Great Britain we began to modify GCC 2.8.1, BINUTILS 2.9.1 and GLIBC 2.1 to
   understand the ELF binary format on the ARM port of Linux we use on the
   NetWinder.  Today we now have a complete functioning ELF Linux system allowing
   to run XFree86, KDE, WordPerfect etc.  More to the point for this list, is the
   fact that I modified GDB 4.17 to run on the NetWinder and would like to
   contribute these changes to the open source community.

Cool!  I'd certainly like to get these into 4.18 if possible!

   A copyright assignment for GLIBC was signed November 25 for GLIBC and all our
   changes have now been integrated into the CVS source tree. I received word on
   December 11 that the Corel now has copyright assignments in place for GCC,
   BINUTILS, and GDB.  So that leads me to following: I would like to contribute
   the code if you are interested.

I don't think I've seen a note from the FSF yet, but sometimes it takes
a couple weeks.

   My patches are not based on the latest snapshot, and are admittedly not
   perfect.  But if no one is working on this and you are interested I would like
   to contribute my code, fix up the problems, and actively maintain the port. 
   Assuming you are interested, and no one else is working on it (there wasn't in
   the last snapshot, but I haven't checked the one announced today) what is the
   best way to approach this.

Send your diffs (-p preferably) from the base version you started
with, to gdb-patches@cygnus.com, and we can start sorting things.  If
you could spare some time to look at a recent snapshot and see how
your patches would play with that, it would help in speeding things
along.  Martin Hunt (hunt@cygnus.com) has expressed a special interest
in this, feel free to correspond with him directly also.

Thanks again for contributing to GDB!

								Stan


      reply	other threads:[~1998-12-24 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-16 20:23 Scott Bambrough
1998-12-24 14:54 ` Stan Shebs [this message]

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=199812242254.OAA07707@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=scottb@corelcomputer.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