From: Jakub Jelinek <jakub@redhat.com>
To: Kai Tietz <ktietz70@googlemail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch fold-const.c]: Add some missing optimizations about binary and and truth-not
Date: Mon, 20 Jun 2011 12:20:00 -0000 [thread overview]
Message-ID: <20110620120640.GC16443@tyan-ft48-01.lab.bos.redhat.com> (raw)
In-Reply-To: <BANLkTinbdBtBjqmA_35ziCu4YXfKUB7R+g@mail.gmail.com>
On Mon, Jun 20, 2011 at 01:50:26PM +0200, Kai Tietz wrote:
> > Ok.
> > Richard.
>
> Applied at revision 175206 to trunk.
There is no need to post such notices to gcc-patches, we have the gcc-cvs
mailing list where this is automatically posted to.
On gcc-patches it just adds unnecessary noise.
Jakub
next prev parent reply other threads:[~2011-06-20 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 11:04 Kai Tietz
2011-06-20 11:50 ` Richard Guenther
2011-06-20 12:16 ` Kai Tietz
2011-06-20 12:20 ` Jakub Jelinek [this message]
2011-06-20 14:43 ` NightStrike
2011-06-20 15:04 ` Jakub Jelinek
2011-06-20 15:38 ` NightStrike
2011-06-20 16:16 ` Jeff Law
2011-06-20 17:56 ` Mike Stump
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=20110620120640.GC16443@tyan-ft48-01.lab.bos.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ktietz70@googlemail.com \
--cc=richard.guenther@gmail.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).