From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Michael Snyder <msnyder@cygnus.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: Allow current CVS libbfd to build with cc on Tru64 UNIX V5.1
Date: Mon, 30 Jul 2001 10:41:00 -0000 [thread overview]
Message-ID: <15205.39983.90091.972062@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <3B659A84.D801B17A@cygnus.com>
Michael Snyder writes:
> I think the change is good, but I'm not sure if this is
> the right mailing list for it. Where do we send bfd changes?
> To binutils?
I think binutils is right. At least that's what I found in the toplevel
MAINTAINERS file. That's why I've sent the patch there, with a copy to
gdb-patches since at the moment gdb on Tru64 UNIX was the affected program.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
Email: ro@TechFak.Uni-Bielefeld.DE
prev parent reply other threads:[~2001-07-30 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 11:58 Rainer Orth
2001-07-30 10:37 ` Michael Snyder
2001-07-30 10:41 ` Rainer Orth [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=15205.39983.90091.972062@xayide.TechFak.Uni-Bielefeld.DE \
--to=ro@techfak.uni-bielefeld.de \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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