public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@synopsys.com>
To: Dan Kegel <dank-gcc@kegel.com>
Cc: "Michael S.Zick" <mszick@goquest.com>,
	Alexandre Oliva <aoliva@redhat.com>,
	Joel Sherrill <joel.sherrill@OARcorp.com>,
	Paul Koning <pkoning@equallogic.com>,
	janis187@us.ibm.com, pbarada@mail.wm.sps.mot.com,
	zack@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: PROPOSAL: Policy for obsoleting targets
Date: Tue, 20 May 2003 00:08:00 -0000	[thread overview]
Message-ID: <20030519164905.A8310@synopsys.com> (raw)
In-Reply-To: <3EC9720B.2070602@kegel.com>; from dank-gcc@kegel.com on Mon, May 19, 2003 at 05:08:43PM -0700



I wrote:
> >>So, suppose we start a web page with Joel's categories as headings, and
> >>then let people fill in sections for instructions in places where they
> >>know the answer?  We'll wind up with missing sections, but at least we'll
> >>have something to point people to.

Michael S.Zick wrote:
> > Perhaps establishing a Wiki would be the answer here.
> > It is such a diverse subject (cross-building) with many people having just
> > the bits and pieces that work for them; it sounds like an ideal subject for
> > a Wiki.

On Mon, May 19, 2003 at 05:08:43PM -0700, Dan Kegel wrote:
> Like, say, the one at http://billgatliff.com/twiki/bin/view/Crossgcc/WebHome ?
> (though I don't much like wikis, and that one's a bit out of date...)
> 
> For what it's worth, over on the crossgcc mailing list, we're trying
> to update Bill Gatliff's toolchain build script.
> See also http://www.embeddedtux.org/pipermail/etux/2003-May/000018.html

I don't object to wikis, but I'd prefer to wind up with an organized
document, that would document a flow that we'd then try to keep working
(at least for the common cases).

  reply	other threads:[~2003-05-19 23:49 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 16:08 Zack Weinberg
2003-05-16 16:31 ` Peter Barada
2003-05-16 17:42   ` Joel Sherrill
2003-05-16 18:30     ` DJ Delorie
2003-05-16 19:19     ` E. Weddington
2003-05-16 22:09       ` Joel Sherrill
2003-05-16 20:16     ` Janis Johnson
2003-05-16 22:10       ` Joel Sherrill
2003-05-16 22:51         ` Janis Johnson
2003-05-16 22:25       ` Paul Koning
2003-05-16 22:34         ` Joel Sherrill
2003-05-16 22:56           ` Alexandre Oliva
2003-05-17  0:02             ` Joe Buck
2003-05-18  6:16               ` Daniel Jacobowitz
2003-05-21 16:46                 ` Jason Thorpe
2003-05-19 22:51               ` Michael S. Zick
2003-05-19 23:46                 ` Dan Kegel
2003-05-20  0:08                   ` Joe Buck [this message]
2003-05-22  2:31               ` Ben Elliston
2003-05-22  5:42                 ` Dan Kegel
2003-05-22 12:22                   ` Michael S. Zick
2003-05-19  2:28         ` Peter Barada
2003-05-19 13:20           ` Paul Koning
2003-05-16 16:34 ` Joe Buck
2003-05-16 17:04   ` Joseph S. Myers
2003-05-16 21:12     ` Joe Buck
2003-05-16 21:21       ` Joseph S. Myers
2003-05-21 16:35       ` Jason Thorpe
2003-05-21 22:02         ` Michael S. Zick
2003-05-16 19:29   ` Daniel Jacobowitz
2003-05-16 16:59 ` Jan Vroonhof
2003-05-18 14:22 ` Marc Espie
2003-05-19 18:28   ` Joe Buck
2003-05-21 17:12   ` Jason Thorpe
2003-05-21 17:49     ` Dan Kegel
2003-05-21  5:25 ` Zack Weinberg
2003-05-21 14:01   ` Michael S. Zick
2003-05-21 16:56   ` Dan Kegel
2003-05-19 18:49 Karim Yaghmour

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=20030519164905.A8310@synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=aoliva@redhat.com \
    --cc=dank-gcc@kegel.com \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=joel.sherrill@OARcorp.com \
    --cc=mszick@goquest.com \
    --cc=pbarada@mail.wm.sps.mot.com \
    --cc=pkoning@equallogic.com \
    --cc=zack@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).