From: Leehod Baruch <LEEHOD@il.ibm.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org, Steven Bosscher <stevenb@suse.de>,
Mircea Namolaru <NAMOLARU@il.ibm.com>
Subject: Re: Searching for a branch for the see optimization.
Date: Wed, 24 Aug 2005 08:10:00 -0000 [thread overview]
Message-ID: <OF6E1E592D.63349A74-ONC2257067.002980EC-C2257067.002B74EF@il.ibm.com> (raw)
In-Reply-To: <430B8C27.7050507@codesourcery.com>
> > Why not just maintain it in a local tree and post refined
> > versions every now and then, until stage 1 for GCC 4.2 opens?
> > Branches are for major work and a new pass is not that major.
>
> It's also fine to create a new branch for this work. That let's other
> people see what you're working on.
That was my original purpose of searching for a brunch.
I thought that if there is a related branch open I could join in.
I don't think that it will disturb other people work.
Leehod.
prev parent reply other threads:[~2005-08-24 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 12:46 Leehod Baruch
2005-08-22 14:27 ` Steven Bosscher
2005-08-23 21:46 ` Mark Mitchell
2005-08-24 8:10 ` Leehod Baruch [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=OF6E1E592D.63349A74-ONC2257067.002980EC-C2257067.002B74EF@il.ibm.com \
--to=leehod@il.ibm.com \
--cc=NAMOLARU@il.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=stevenb@suse.de \
/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).