From: Diego Novillo <dnovillo@redhat.com>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Doing regular trunk->ast-optimizer-branch merges?
Date: Fri, 19 Oct 2001 09:29:00 -0000 [thread overview]
Message-ID: <20011019122852.A9929@tornado.cygnus.com> (raw)
In-Reply-To: <3BCEAC8B.9BB8452E@codesourcery.com>
On Thu, 18 Oct 2001, Nathan Sidwell wrote:
> Diego Novillo wrote:
> > Now, I remember that you wanted to work on a stable branch, so
> > maybe it would be better if we just create a new branch for the
> > tree SSA work?
>
> As you've probably noticed, I've not done any work on that branch for a
> while now. You've been using it much more than me, so merge away. If
> it becomes a problem, I'm sure we can work something out.
>
Well, I got started with the merge but I won't be able to fix all
the conflicts today. Since I won't be able to work on this for
a while, it'll have to wait a bit longer.
Diego.
prev parent reply other threads:[~2001-10-19 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 7:44 Diego Novillo
2001-10-18 14:39 ` Nathan Sidwell
2001-10-18 9:05 ` Diego Novillo
2001-10-19 9:29 ` Diego Novillo [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=20011019122852.A9929@tornado.cygnus.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=nathan@codesourcery.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).