From: Richard Henderson <rth@redhat.com>
To: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
Cc: Roger Sayle <roger@eyesopen.com>,
Paolo Bonzini <paolo.bonzini@lu.unisi.ch>,
gcc-patches@gcc.gnu.org
Subject: Re: [patch] double_int
Date: Tue, 28 Feb 2006 21:39:00 -0000 [thread overview]
Message-ID: <20060228213920.GA28369@redhat.com> (raw)
In-Reply-To: <20060228113806.GA6560@atrey.karlin.mff.cuni.cz>
On Tue, Feb 28, 2006 at 12:38:07PM +0100, Zdenek Dvorak wrote:
> Comments (not neccessarily regarding just this change)?
I'm ok with this approach.
r~
next prev parent reply other threads:[~2006-02-28 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 15:58 Patch ping Zdenek Dvorak
2006-02-17 2:40 ` Roger Sayle
2006-02-17 9:24 ` Zdenek Dvorak
2006-02-17 10:34 ` Paolo Bonzini
2006-02-17 15:31 ` Roger Sayle
2006-02-21 9:15 ` Zdenek Dvorak
2006-02-21 14:47 ` Roger Sayle
2006-02-21 15:43 ` Zdenek Dvorak
2006-02-21 18:01 ` Richard Henderson
2006-02-21 23:04 ` Zdenek Dvorak
2006-02-21 23:16 ` Richard Henderson
2006-02-22 0:20 ` Zdenek Dvorak
2006-02-28 11:38 ` [patch] double_int Zdenek Dvorak
2006-02-28 21:39 ` Richard Henderson [this message]
2006-03-02 2:58 ` Roger Sayle
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=20060228213920.GA28369@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paolo.bonzini@lu.unisi.ch \
--cc=rakdver@atrey.karlin.mff.cuni.cz \
--cc=roger@eyesopen.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).