From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Andrey Belevantsev <abel@ispras.ru>
Subject: Re: [PATCH][PING] Fix scheduling at the end of blocks.
Date: Tue, 03 Jun 2008 15:00:00 -0000 [thread overview]
Message-ID: <48455C67.8020507@codesourcery.com> (raw)
In-Reply-To: <47ECFBC3.6080701@redhat.com>
Vladimir Makarov wrote:
> Maxim Kuvyrkov wrote:
>> Maxim Kuvyrkov wrote:
>>> Vladimir Makarov wrote:
>>
>> ...
>>
>>>> Maxim, please ping me when the mainline will be at stage 1.
>>
>> Hello Vladimir,
>>
>>
>> Ping.
>>
>>
> Sorry, I'll do the review on next week.
Hello Vladimir,
Ping again. Just a remainder, no pressure.
--
Maxim
prev parent reply other threads:[~2008-06-03 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 20:37 [PATCH] " Maxim Kuvyrkov
2007-12-05 21:37 ` Maxim Kuvyrkov
2007-12-05 22:02 ` Richard Guenther
2007-12-06 11:33 ` Maxim Kuvyrkov
2007-12-10 18:01 ` Vladimir Makarov
2008-03-14 12:21 ` Maxim Kuvyrkov
2008-03-28 15:57 ` [PATCH][PING] " Maxim Kuvyrkov
2008-03-28 18:23 ` Vladimir Makarov
2008-06-03 15:00 ` Maxim Kuvyrkov [this message]
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=48455C67.8020507@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=abel@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=vmakarov@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).