From: Joel Brobecker <brobecker@adacore.com>
To: Denis PILAT <denis.pilat@st.com>,
Andrew STUBBS <andrew.stubbs@st.com>,
gdb-patches <gdb-patches@sourceware.org>,
Ilko Iliev <iliev@ronetix.at>
Subject: Re: [rfc] Overflow in transfer-rate
Date: Wed, 04 Jul 2007 17:19:00 -0000 [thread overview]
Message-ID: <20070704172111.GB6035@adacore.com> (raw)
In-Reply-To: <20070703153213.GB2868@caradoc.them.org>
> I've committed it. I don't know when Joel is planning to date the
> branch, but I think it will be in 6.7.
I am about to start working on the branch. I'm trying to catch up
a bit on the last patches that went in to see where it would be most
beneficial to branch. I have updated the Wiki to make sure that this
patch makes it to the branch.
--
Joel
next prev parent reply other threads:[~2007-07-04 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 12:05 Denis PILAT
2007-06-11 12:52 ` Andrew STUBBS
2007-06-11 13:15 ` Denis PILAT
2007-07-01 22:10 ` Daniel Jacobowitz
2007-07-02 7:36 ` Denis PILAT
2007-07-03 15:32 ` Daniel Jacobowitz
2007-07-04 17:19 ` Joel Brobecker [this message]
2007-07-04 18:00 ` Mark Kettenis
2007-07-04 18:15 ` Daniel Jacobowitz
2007-07-04 18:20 ` Joel Brobecker
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=20070704172111.GB6035@adacore.com \
--to=brobecker@adacore.com \
--cc=andrew.stubbs@st.com \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sourceware.org \
--cc=iliev@ronetix.at \
/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