From: Manoj Iyer <manjo@austin.ibm.com>
To: Randolph Chung <randolph@tausq.org>
Cc: Andrew Cagney <cagney@gnu.org>,
Joel Brobecker <brobecker@gnat.com>,
gdb@sources.redhat.com
Subject: Re: GDB 6.1.1 2004-05-21-gmt
Date: Wed, 26 May 2004 22:13:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0405261653390.31396@lazy> (raw)
In-Reply-To: <20040525222803.GQ7207@tausq.org>
I have similar issues with GDB 6.1 wrt ppc64, there are many changes in
mainline that I would like to have in 6.1, so my question is... When will
6.2 be released?
--
Manoj
On Tue, 25 May 2004, Randolph Chung wrote:
> > There seem to be a significant number of fixes even without this -
> > basics such as value return and backtraces.
> >
> > As for the arch and other core changes, they can wait until 6.2.
>
> ok... it's just that the gdbarch change will fix MANY problems in the
> testsuite. :)
>
> what is the process for getting patches into 6.1? Are they resubmitted
> one-by-one, or do i do a wholesale diff of hppa-specific files? There
> are about 30 patches from me that has gone into CVS since 6.1.
>
> thanks
> randolph
> --
> Randolph Chung
> Debian GNU/Linux Developer, hppa/ia64 ports
> http://www.tausq.org/
>
next prev parent reply other threads:[~2004-05-26 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 21:22 Andrew Cagney
2004-05-25 21:36 ` Randolph Chung
2004-05-25 21:47 ` Joel Brobecker
2004-05-25 21:53 ` Randolph Chung
2004-05-25 22:22 ` Andrew Cagney
2004-05-25 22:28 ` Randolph Chung
2004-05-26 17:15 ` Andrew Cagney
2004-05-26 18:10 ` Randolph Chung
2004-05-26 22:13 ` Manoj Iyer [this message]
2004-05-27 20:19 ` Andrew Cagney
2004-05-26 17:58 ` Andrew Cagney
2004-06-07 18:18 ` GDB 6.1.1 2004-05-21-gmt [not] Andrew Cagney
2004-05-26 0:08 GDB 6.1.1 2004-05-21-gmt Michael Elizabeth Chastain
2004-05-27 10:54 Michael Elizabeth Chastain
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=Pine.LNX.4.58.0405261653390.31396@lazy \
--to=manjo@austin.ibm.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=randolph@tausq.org \
/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