From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Kevin Buettner <kevinb@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/ppc/branch too] Fix PowerPC/Linux cores
Date: Tue, 31 Jul 2001 08:50:00 -0000 [thread overview]
Message-ID: <3B66D3A5.10203@cygnus.com> (raw)
In-Reply-To: <20010730175738.A23859@nevyn.them.org>
>> Before you commit anything along these lines (or along the lines of
>> the patch that you submitted), do check with Andrew first. I'm not
>> the core-regset.c maintainer and Andrew may want to see all patches
>> that go in on the release branch go in on the trunk as well...
>
>
> OK. In that case, I think the right thing to do would be:
> - remove the #ifdefs
> - change to the gdb_*regset_t functions
> On both branch and trunk. I thought more platforms had custom
> GDB_GREGSET_T definitions, but I guess not.
>
> It's closer to overall right, and it will still go away in a reasonable
> amount of time. I'd rather not diverge the branch and truck if I don't
> have to.
>
> Andrew, how's that sound?
Well, the one thing I don't want is hacks pulled on the branch that
aren't matched in the trunk - people will assume bugs are fixed when
they are not. Pulling the same tweek on both is ok.
Beyond that it is between you and Kevin.
Andrew
next prev parent reply other threads:[~2001-07-31 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 14:23 Daniel Jacobowitz
2001-07-30 15:44 ` Kevin Buettner
2001-07-30 15:54 ` Daniel Jacobowitz
2001-07-30 17:50 ` Kevin Buettner
2001-07-30 17:57 ` Daniel Jacobowitz
2001-07-31 8:50 ` Andrew Cagney [this message]
2001-08-02 12:08 ` Daniel Jacobowitz
2001-08-02 12:48 ` Kevin Buettner
2001-08-03 8:39 ` Andrew Cagney
2001-08-03 14:36 ` Daniel Jacobowitz
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=3B66D3A5.10203@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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