public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for August
Date: Thu, 03 Aug 2006 08:23:48 -0400	[thread overview]
Message-ID: <1154607828.23292.5.camel@localhost> (raw)
In-Reply-To: <44D1BFFD.4040303@gentoo.org>

On Thu, 2006-08-03 at 11:21 +0200, Jakub Moc wrote:
> Mike Frysinger wrote:
> > This is your monthly friendly reminder !  Same bat time (typically the
> > 2nd Thursday once a month), same bat channel (#gentoo-council @
> > irc.freenode.net) !
> 
> Would like the Council to discuss the current state of Gentoo Bugzilla
> [1] and anon CVS/SVN [2].

Please elaborate why you need the council to discuss 
ongoing active bugs that are in progress.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-03 12:27 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for August Mike Frysinger
2006-08-01 11:13 ` Wernfried Haas
2006-08-14 17:23   ` Thierry Carrez
2006-08-15  9:22     ` Stuart Herbert
2006-08-03  9:21 ` Jakub Moc
2006-08-03 12:23   ` Ned Ludd [this message]
2006-08-03 13:06     ` Lance Albertson
2006-08-03 13:35       ` Ned Ludd
2006-08-03 14:07         ` Jakub Moc
2006-08-03 14:48           ` Ned Ludd
2006-08-03 15:05             ` Jakub Moc
2006-08-03 13:20               ` Alec Warner
2006-08-03 18:08                 ` Patrick Lauer
2006-08-03 18:48                   ` Lance Albertson
2006-08-03 19:22                     ` Patrick Lauer
2006-08-04  4:58                       ` Jochen Maes
2006-08-03 19:55                     ` Chris Bainbridge
2006-08-03 20:54                       ` kashani
2006-08-03 21:10                         ` Lance Albertson
2006-08-04  8:15                           ` Simon Stelling
2006-08-04 13:13                             ` Lance Albertson
2006-08-03 20:55                       ` Lance Albertson
2006-08-04  5:06                   ` Jochen Maes
2006-08-03 18:51                 ` Lance Albertson
2006-08-03 19:02                   ` Ciaran McCreesh
2006-08-03 19:21                     ` Lance Albertson
2006-08-04  5:07                     ` Jochen Maes
2006-08-03 17:03               ` Simon Stelling
2006-08-03 17:55                 ` Patrick Lauer
2006-08-03 14:58           ` Lance Albertson
2006-08-03 15:10             ` Jakub Moc
2006-08-04  8:57         ` Curtis Napier
2006-08-04  9:07           ` Curtis Napier
     [not found]           ` <44D34753.6090604@gentoo.org>
2006-08-04 15:53             ` Joshua Jackson
2006-08-04 16:08               ` Alec Warner
2006-08-04 19:23                 ` Mike Doty
2006-08-04 18:07               ` kashani
2006-08-04 19:56                 ` Robin H. Johnson
     [not found] <886253338-1154701653-cardhu_blackberry.rim.net-693078490-@bwe059-cell00.bisx.prod.on.blackberry>
2006-08-04 23:22 ` Matthew Marlowe
  -- strict thread matches above, loose matches on Subject: below --
2007-08-01  8:08 Mike Frysinger
2007-08-01 13:14 ` Mike Frysinger
2008-08-01  5:30 Mike Frysinger
2009-08-01  5:30 Mike Frysinger
2009-08-01 13:10 ` Sebastian Pipping
2009-08-02 15:58   ` Denis Dupeyron

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=1154607828.23292.5.camel@localhost \
    --to=solar@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