From: "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com>
To: gdb-patches@sources.redhat.com
Subject: More code code dropping
Date: Thu, 06 Dec 2001 22:41:00 -0000 [thread overview]
Message-ID: <200112070641.WAA01521@localhost.localdomain> (raw)
In-Reply-To: <20011129005901.A60085@molenda.com>
Ada Core Techologies, Inc., is also in possession of a large set of
modifications to GDB to make it Ada aware, which require quite a bit more
processing to turn into patches. So, like Apple, we'd like to deposit
this heap o'code in a spot more convenient to the general public. Not having
done this before, however, I'd appreciate knowing the appropriate procedure
for making such a deposit.
Paul Hilfinger
ACT, Inc.
next parent reply other threads:[~2001-12-07 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011129005901.A60085@molenda.com>
2001-12-06 22:41 ` Paul N. Hilfinger [this message]
2001-12-07 7:32 ` 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=200112070641.WAA01521@localhost.localdomain \
--to=hilfingr@otisco.mckusick.com \
--cc=Hilfinger@otisco.mckusick.com \
--cc=gdb-patches@sources.redhat.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