From: Christian Faulhammer <fauli@gentoo.org>
To: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Cc: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Patches for your reviewing pleasure: Various improvements, including cheat sheet
Date: Tue, 14 Apr 2009 10:44:48 +0200 [thread overview]
Message-ID: <20090414104448.20153bfb@terra.solaris> (raw)
In-Reply-To: <20090413170143.31087b9c@snowcone>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
Hi,
Ciaran McCreesh <ciaran.mccreesh@googlemail.com>:
> > In the long term we should move the chapter files into a "chapters"
> > subdirectory. I can create a patch for that.
>
> Why do we need subdirectories? So far as I can see we're a long way
> off, and probably won't ever reach, the point where things are
> unmanageable without them.
It isn't about managing the files but about getting into the code. A
root directory with only five files is easier to grasp for a
beginner than with 20. The move isn't hard, so we can do this at every
point in the future.
> > I wanted to add it when all labels for all EAPIs are ready.
>
> I thought they were. Didn't I do labels for 1 and 2 things?
I wasn't sure if they were complete...anyway, I now have EAPI 3
properly referenced. You want that version or should I go through 1
and 2, also?
> > The long abstract was needed to fill the first page, it looked so
> > empty in the first version. So I will cut it down.
>
> Stick a picture of a cow there or something.
I now have EAPI 0 described, so a shorter abstract should do it.
V-Li
--
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
<URL:http://gentoo.faulhammer.org/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-04-14 8:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-12 19:14 [gentoo-pms] Patches for your reviewing pleasure: Various improvements, including cheat sheet Christian Faulhammer
2009-04-12 19:36 ` Ciaran McCreesh
2009-04-13 9:01 ` Christian Faulhammer
2009-04-13 16:01 ` Ciaran McCreesh
2009-04-14 8:44 ` Christian Faulhammer [this message]
2009-04-14 13:04 ` Ciaran McCreesh
2009-04-14 13:55 ` Christian Faulhammer
2009-04-14 14:46 ` Ciaran McCreesh
2009-04-15 15:28 ` Christian Faulhammer
2009-04-15 20:35 ` Ciaran McCreesh
2009-04-15 21:58 ` Christian Faulhammer
2009-04-15 22:10 ` Ciaran McCreesh
2009-04-15 22:46 ` Christian Faulhammer
2009-04-16 14:16 ` Ciaran McCreesh
2009-04-16 22:23 ` Christian Faulhammer
2009-04-17 14:11 ` Yannick Mortier
2009-04-12 21:25 ` David Leverton
2009-04-13 9:05 ` Christian Faulhammer
2009-04-13 21:16 ` [gentoo-pms] [PATCH] Work around TeX4ht being weird David Leverton
2009-04-14 8:32 ` Christian Faulhammer
2009-04-15 19:03 ` David Leverton
2009-04-15 21:59 ` Christian Faulhammer
2009-04-16 7:25 ` David Leverton
2009-04-16 19:37 ` [gentoo-pms] [PATCH 1/2] " David Leverton
2009-04-16 19:37 ` [gentoo-pms] [PATCH 2/2] Update TeX4ht sed hacks David Leverton
2009-04-16 19:42 ` Ciaran McCreesh
2009-04-17 14:13 ` Yannick Mortier
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=20090414104448.20153bfb@terra.solaris \
--to=fauli@gentoo.org \
--cc=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@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