public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] livecd-stage1 problem
Date: Thu, 13 Mar 2008 10:03:23 -0700	[thread overview]
Message-ID: <1205427803.7261.27.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <47D7F351.8040904@optaros.com>

[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]

On Wed, 2008-03-12 at 11:14 -0400, Robert C Corsaro wrote:
> > Also, the wiki is *not* an official source of Gentoo .  I wish people
> > would realize that.
> > 
> 
> I think that the problem is, there is no "official documentation" AFAIK.

Yes, there is.  Try to emerge catalyst again and read what it actually
says.  There is no *web* documentation.

>   The catalyst page points to the newbie wiki as the best source of 
> documentation.  It was the only path I could find to understanding how 
> to use catalyst.  Saying it's not official documentation is fine, but it

Umm... no.  The catalyst page most definitely does *not* point to
*anything* on gentoo-wiki.  I'm guessing you mean some random catalyst
page on gentoo-wiki, don't you?

> will still help reduce the amount of questions asked here to try and 
> make it 'right'(which I have no problem doing).  I'm sorry if the 
> information I was looking for is written down somewhere and I didn't 
> find it.  If it is, perhaps we can add that docs location to the 
> catalyst page.  I did search the mailing list archive and didn't see my 
> problem.  Maybe I didn't look hard enough?  If not, sorry for wasting 
> time.  I know it sucks to answer the same question over and over.

Every livecd-stage1 "blocker" issue ever reported has been this same
issue.  I know it's hit this list a few times, but would likely be
difficult to search and find, since I bet most people would search for
the package in question, rather than the action being taken.

> BTW, catalyst is awesome, so thanks to everyone who worked on it.

Well, check out AUTHORS and send them beer.  ;]

-- 
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-03-13 17:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 19:45 [gentoo-catalyst] livecd-stage1 problem Robert C Corsaro
2008-03-11 19:48 ` Andrew Gaffney
2008-03-11 19:51   ` Robert C Corsaro
2008-03-11 19:54     ` Andrew Gaffney
2008-03-12  4:33     ` Daniel Díaz
2008-03-13 17:00       ` Chris Gianelloni
2008-03-12 14:59 ` Chris Gianelloni
2008-03-12 15:14   ` Robert C Corsaro
2008-03-12 15:21     ` Andrew Gaffney
2008-03-12 15:25       ` Robert C Corsaro
2008-03-13 17:13         ` Chris Gianelloni
2008-03-13 17:03     ` Chris Gianelloni [this message]
2008-03-13 17:16       ` Robert C Corsaro
2008-03-13 17:22         ` Chris Gianelloni
2008-03-14  0:23           ` Daniel Díaz
2008-03-27  6:42             ` Chris Gianelloni
2008-04-04  2:43               ` Daniel Díaz

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=1205427803.7261.27.camel@inertia.twi-31o2.org \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-catalyst@lists.gentoo.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