From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: PATCH: Fix gdb build failure
Date: Tue, 01 Apr 2003 14:37:00 -0000 [thread overview]
Message-ID: <3E89A412.7000902@redhat.com> (raw)
In-Reply-To: <20030401141806.GA13158@nevyn.them.org>
> I changed the interface of a function in BFD yesterday and forgot to update
> the one call to it in GDB. Sorry 'bout that. Fixed with the attached.
FYI, a better way of doing this is to introduce a new method and then
mark the current one as obsolete. There's a bfd macro containing a
version date available for this. I'm not talking months here, just
weeks. That gives the two directories a bit of leway so that if one
fails, the other can revert and survive :-)
Andrew
prev parent reply other threads:[~2003-04-01 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 14:18 Daniel Jacobowitz
2003-04-01 14:37 ` Andrew Cagney [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=3E89A412.7000902@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.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