From: Diego Novillo <dnovillo@redhat.com>
To: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Tree flags vs. tree-ssa merge
Date: Mon, 22 Mar 2004 18:27:00 -0000 [thread overview]
Message-ID: <1079969185.31835.68.camel@localhost.localdomain> (raw)
In-Reply-To: <10403221528.AA13231@vlsi1.ultra.nyu.edu>
On Mon, 2004-03-22 at 10:28, Richard Kenner wrote:
> Would you be willing to apply your patch to tree-ssa at the same time?
>
> I don't currently have that branch checked out or have set up testing
> procedures for it, so I think that would be a bad idea.
>
So, you aren't willing to help with merge conflicts?
Diego.
next prev parent reply other threads:[~2004-03-22 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 18:21 Richard Kenner
2004-03-22 18:27 ` Diego Novillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-22 18:57 Richard Kenner
2004-03-22 21:52 ` Diego Novillo
2004-03-22 18:30 Richard Kenner
2004-03-22 18:45 ` Diego Novillo
2004-03-22 16:34 Richard Kenner
2004-03-22 17:45 ` Diego Novillo
2004-03-22 18:33 ` law
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=1079969185.31835.68.camel@localhost.localdomain \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).