From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Who wrote the parisc gdb support?
Date: Fri, 27 Dec 2002 15:36:59 -0500 [thread overview]
Message-ID: <20021227203659.GC1014@systemhalted> (raw)
In-Reply-To: <20021227110244.GY24337@sleepie.demon.co.uk>
> > Taggart said it was dhd and amodra mostly.
> > I think he is right.
> > IIRC, Most, if not all, of the work was funded by HP under contract
> > with Linuxcare in fall 2000 and spring 2001.
>
> I'd agree with that. At one time I worked on kernel support for it,
> while amodra worked on gdb itself. We were both working for Linuxcare,
> under contract to HP at the time.
>
That's good then, since the chain of copyright now goes like this:
Linuxcare -> HP -> FSF
It's rogue hackers without copyright assignment that do more than
trivial patches that worry me... not naming any names *cough* tausq
*cough* Though that person now has all the papers in place ;)
c.
prev parent reply other threads:[~2002-12-27 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 2:07 [parisc-linux] Who wrote the parisc gdb support? Carlos O'Donell
2002-12-27 6:20 ` Grant Grundler
2002-12-27 11:02 ` Richard Hirst
2002-12-27 20:36 ` Carlos O'Donell [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=20021227203659.GC1014@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rhirst@linuxcare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.