public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [DREAMCAST] : Buildfailure
Date: Mon, 31 Dec 2007 17:34:22 +0000	[thread overview]
Message-ID: <20071231173422.GA23694@linux-sh.org> (raw)
In-Reply-To: <20071229004013.9a05bbd6.Kristoffer.Ericson@Gmail.com>

On Mon, Dec 31, 2007 at 05:02:07PM +0000, michiegan@eircom.net wrote:
> Primarily I'm in this for the learning curve so I prefer doing
> everything by hand so I know what's going on, I know where everything
> is, and I'm hopelessly masochistic!
[snip]

> From your toolchain wiki page, it says that gcc-4.0.1 is as up-to-date
> as it gets. obviously the wiki page isn't up to date.
[more snippage]

Yes, it's quite possibly outdated in a lot of areas. Most of the stuff
documented is unrelated to specific version, so it's probably better to
just leave the versions ambiguous.

If you run in to issues with the wiki, either note them down and submit a
report to the list, or (preferred option) simply fix them up as you go
along. It's certainly our intent to have the wiki as useful as possible
for people, but obviously some content falls behind faster than others.

It would also be good to have an indicator of content that you feel is
missing from the wiki, or things that need to be expanded on to improve
clarity for those approaching these topics for the first time.

      parent reply	other threads:[~2007-12-31 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 23:40 [DREAMCAST] : Buildfailure Kristoffer Ericson
2007-12-30  3:06 ` Paul Mundt
2007-12-31 17:34 ` Paul Mundt [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=20071231173422.GA23694@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.org \
    /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