public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Drake Wyrm <wyrm@haell.com>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New Portage Category: dev-scheme
Date: Tue, 27 Jan 2004 07:16:16 -0500	[thread overview]
Message-ID: <1075205776.15976.0.camel@localhost> (raw)
In-Reply-To: <20040127091451.GA9009@phaenix.haell.com>

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

On Tue, 2004-01-27 at 04:14, Drake Wyrm wrote:
> On Tue, Jan 27, 2004 at 03:02:23AM -0500, in
> <20040127080223.GB5541@dev.gentoo.org>, Blake Matheny <jake@gentoo.org>
> wrote:
> > Whatchu talkin' 'bout, Willis?
> > > I think dev-cl doesnt tell much, might be better to have something like
> > > dev-clisp.. and while we're at it.. dev-lisp...
> > Not what I was suggesting. As seemant said, I think a good direction to go
> > would be lisp-clisp, lisp-scheme, etc as the game categories have done.
> I know convention states that categories will be named <type>-<subtype>
> and, by the "games" precedent, split into <subtype>-<subsubtype> when
> necessary. Is there anything that actually stops us from using more than
> one dash in a category name? I can see that this opens a huge can-o-worms,
> but how about dev-lisp, dev-lisp-clisp, dev-lisp-scheme, etc.?

I am pretty sure that categories can only have one dash.  At least I
know that was true, but I am not positive if it still holds to be the
same.

-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a penguin?

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

  reply	other threads:[~2004-01-27 12:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-24 21:57 [gentoo-dev] New Portage Category: dev-scheme Blake Matheny
2004-01-24 22:54 ` Matthew Kennedy
2004-01-26  9:07 ` Grant Goodyear
2004-01-26 17:26   ` Blake Matheny
2004-01-26 18:05     ` Brian Friday
2004-01-26 19:07       ` Matthew Kennedy
2004-01-26 19:19         ` Thomas de Grenier de Latour
2004-01-27  3:26           ` Blake Matheny
2004-01-27  3:49         ` Drake Wyrm
2004-01-27  5:08           ` Seemant Kulleen
2004-01-27  5:37             ` Blake Matheny
2004-01-27  6:47               ` Olivier Crête
2004-01-27  8:02                 ` Blake Matheny
2004-01-27  9:14                   ` Drake Wyrm
2004-01-27 12:16                     ` Chris Gianelloni [this message]
2004-01-27 13:29                     ` Jean Jordaan
2004-01-27 18:25                       ` George Shapovalov
2004-01-27 18:34                 ` Matthew Kennedy
2004-01-27 18:56           ` Matthew Kennedy

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=1075205776.15976.0.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=wyrm@haell.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