public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dominique Michel <dominique.michel@citycable.ch>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: new herd: theology
Date: Sat, 28 Apr 2007 18:32:50 +0200	[thread overview]
Message-ID: <20070428183250.68881282@localhost> (raw)
In-Reply-To: <pan.2007.04.28.13.16.26@cox.net>

Le Sat, 28 Apr 2007 13:16:27 +0000 (UTC),
Duncan <1i5t5.duncan@cox.net> a écrit :

> Thomas Rösner <Thomas.Roesner@digital-trauma.de> posted
> 4633408F.5030507@digital-trauma.de, excerpted below, on  Sat, 28 Apr 2007
> 14:39:43 +0200:
> 
> 
> Indeed.  That's why while I don't personally agree with the idea of 
> genealogy in theology, I think it goes in sci-*, I also don't believe 
> it's a big deal in terms of herd placement.  Herd placement is primarily 
> of "internal Gentoo interest", that is, to Gentoo devs/ATs/etc, not even 
> most users except for filing bugs and if it's automated there... . 
> 

I disagree. When searching for a software to do a given job and when I have
no idea of which software can do it, I begin to look for the ebuild descriptions
in the portage tree. It goes faster as anything else with mc. And I will never
search a genealogy program in theology, so I will just miss it if it is in
theology.

That said, I agree at it is not a big deal in term of herd placement from a
developer point of vue, but it is one, as I already said, in term of
consistency and meanings. English is not my first language, and if the
portage tree don't have a good consistency regarding to the meaning of the used
terms, I vote to replace those terms by numbers. So it will be no consistency
problem because it will be no consistency at all. 

I am joking, the name of the herds are fine. And I prefer to have such a
naming policy as something as a/aa/* as on sourceforge.

Ciao,
Dominique
--
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-04-28 16:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27  2:03 [gentoo-dev] new herd: theology Steve Dibb
2007-04-27  4:11 ` Josh Sled
2007-04-27  4:34   ` Andrej Kacian
2007-04-27  5:54     ` Steffen Brumm
2007-04-27  8:18       ` [PROCTORS] " Wernfried Haas
2007-04-27 20:19         ` [gentoo-dev] " Drake Wyrm
2007-04-27 21:48           ` Donnie Berkholz
2007-04-27  5:24   ` [gentoo-dev] " Jeroen Roovers
2007-04-27  7:56     ` Matti Bickel
2007-04-27 13:32       ` Jeroen Roovers
2007-04-27  9:17     ` [gentoo-dev] " Duncan
2007-04-27 10:59       ` Alexandre Buisse
2007-04-27 18:02         ` Dominique Michel
2007-04-28  1:01           ` Steve Dibb
2007-04-28  3:07             ` Josh Saddler
2007-04-28  8:56               ` Dominique Michel
2007-04-28 12:39                 ` Thomas Rösner
2007-04-28 13:16                   ` Duncan
2007-04-28 16:32                     ` Dominique Michel [this message]
2007-04-28 22:27                       ` Duncan
2007-04-29 10:00                         ` Dominique Michel
2007-04-29 10:21                           ` Wulf C. Krueger
2007-04-28 15:54                   ` Alexander Skwar
2007-04-27 11:16       ` Steffen Brumm
2007-04-27 13:09   ` [gentoo-dev] " Steve Dibb
2007-04-28 17:10   ` Rémi Cardona
2007-04-28 17:37     ` Nathan Smith
2007-04-29  1:25       ` Josh Saddler
2007-04-29  7:53         ` Rémi Cardona
2007-04-29  9:55         ` Dominique Michel

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=20070428183250.68881282@localhost \
    --to=dominique.michel@citycable.ch \
    --cc=gentoo-dev@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