public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] C++ herd proposal
Date: Sat, 17 Sep 2005 02:45:37 +0100	[thread overview]
Message-ID: <20050917024537.74c60871@snowdrop.home> (raw)
In-Reply-To: <432B4549.1070400@gentoo.org>

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

On Fri, 16 Sep 2005 18:20:57 -0400 Mark Loeser <halcy0n@gentoo.org>
wrote:
| Since we currently have language herds for other languages such as
| Ada, Perl, and Java, I don't think C++ should be any different.
| There are currently many packages in the tree that are C++ libraries
| or utilities that are no-herd and are actively maintained, and there
| are probably some that have just been sitting around rotting.  With
| the creation of a C++ herd, there would be a team that could support
| these packages, instead of a single maintainer, if the package has
| one.  Below is a list of all of the packages that I believe would
| qualify as falling under this herd.  If you see your name in the
| following list, I'd especially like to hear from you.  Names with a
| '?' next to them are packages that had no metadata and I guessed from
| the changelog who the maintainer is. I would also like to see many of
| them, if not all, moved to the dev-cpp
| category:

I use some of those. Count me in, so long as I don't ever have to touch
the hideous monstrosity that is boost...

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-09-17  1:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 22:20 [gentoo-dev] [RFC] C++ herd proposal Mark Loeser
2005-09-16 23:20 ` Mike Frysinger
2005-09-17 11:31   ` Christian Parpart
2005-09-17  1:34 ` Aaron Walker
2005-09-17  1:45 ` Ciaran McCreesh [this message]
2005-09-17  7:00 ` Robin H. Johnson
2005-09-17  9:36 ` Kevin F. Quinn
2005-09-17 11:33   ` Christian Parpart
2005-09-17 12:01     ` Kevin F. Quinn
2005-09-17 13:27       ` Christian Parpart
2005-09-17 18:22   ` Mark Loeser
2005-09-17 20:14     ` Mike Frysinger
2005-09-17 20:24       ` Mark Loeser
2005-09-19  9:43         ` Paul de Vrieze
2005-09-19 12:33           ` Mark Loeser
2005-09-19 13:22             ` warnera6
2005-09-20  5:21               ` Christian Parpart
2005-09-20  5:37                 ` Georgi Georgiev
2005-09-20  6:37                   ` Alin Nastac
2005-09-20  6:43                     ` Georgi Georgiev
2005-09-20  7:01                       ` Alin Nastac
2005-09-20  7:42                         ` Brian Harring
2005-09-20  6:54                   ` Kevin F. Quinn
2005-09-20  9:09                     ` Martin Schlemmer
2005-09-20 16:32                       ` Donnie Berkholz
2005-09-18 21:46       ` Christian Parpart

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=20050917024537.74c60871@snowdrop.home \
    --to=ciaranm@gentoo.org \
    --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