From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Print trace state variables
Date: Fri, 10 Dec 2010 11:27:00 -0000 [thread overview]
Message-ID: <20101210112600.GA2596@adacore.com> (raw)
In-Reply-To: <4D015A4A.7040500@codesourcery.com>
> If this seems reasonable, I'll put in both trunk and 7.2 branch.
Is this the change that you were thinking we should wait for before
releasing 7.2.1?
Tristan just informed me yesterday of another issue with etc/gnu-oids.texi
missing, and I will backport his change in a second. If all is ready and
in, I should be able to make the release on, say, Monday.
--
Joel
next prev parent reply other threads:[~2010-12-10 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 22:38 Stan Shebs
2010-12-10 11:27 ` Joel Brobecker [this message]
2010-12-10 14:04 ` Stan Shebs
2010-12-10 16:35 ` Marc Khouzam
2010-12-10 20:00 ` Tom Tromey
2010-12-11 5:28 ` Joel Brobecker
2010-12-11 5:55 ` Joel Brobecker
2010-12-13 5:56 ` Stan Shebs
2010-12-13 13:00 ` Pedro Alves
2010-12-14 16:13 ` Tom Tromey
2010-12-13 12:31 ` Hui Zhu
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=20101210112600.GA2596@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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