From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>,
gdb@sources.redhat.com, Joel Brobecker <brobecker@gnat.com>
Subject: GDB 6.1.1 2004-05-21-gmt
Date: Tue, 25 May 2004 21:22:00 -0000 [thread overview]
Message-ID: <40B3B907.2030401@gnu.org> (raw)
It's time for that re-spin. It's ment to happen in may so I'd better do
it before the comming weekend :-/
Randolph, Joel, for HP/PA, should the architecture specific changes
(i.e., hp*-{tdep,nat}) be pulled into the branch?
Andrew
next reply other threads:[~2004-05-25 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 21:22 Andrew Cagney [this message]
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
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=40B3B907.2030401@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--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