From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] livecd-stage1 problem
Date: Wed, 26 Mar 2008 23:42:35 -0700 [thread overview]
Message-ID: <1206600155.7856.9.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <e7df06480803131723vecf5533h829f644e1bc45c47@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
On Thu, 2008-03-13 at 18:23 -0600, Daniel Díaz wrote:
> On Thu, Mar 13, 2008 at 11:22 AM, Chris Gianelloni <wolf31o2@gentoo.org> wrote:
> [...]
> > I plan on starting up a fairly comprehensive manual for catalyst after
> > this coming release.
>
> Chris, if I can be of any help please let me know . Somebody else
> might be interested too in collaborating developing a good reference
> manual.
Absolutely, I plan on starting it simply as a listing of every spec file
key available in each target, but from there, plan on writing up a
simple "howto" which will slowly expand into a comprehensive manual.
I would definitely be interested in help. Do you know GuideXML?
--
Chris Gianelloni
Release Engineering Strategic Lead
Games Developer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-27 6:43 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
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 [this message]
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=1206600155.7856.9.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