public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Saddler <nightmorph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Marking bugs for bugday?
Date: Sun, 28 Feb 2010 17:35:04 -0800	[thread overview]
Message-ID: <20100228173504.78eea0b1@angelstorm> (raw)
In-Reply-To: <4B8ACC34.7000600@gentoo.org>

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

On Sun, 28 Feb 2010 21:04:04 +0100
Sebastian Pipping <sping@gentoo.org> wrote:

> On 02/28/10 20:54, Markos Chandras wrote:
> > Do we still have bugdays? Who is taking care of this project and the 
> > respective webpage? I think we first need to answer these questions before
> > we even consider resurrect this project
> 
> welp         -> away

He's not away, he's retired. It's just taken several months to close his bug.

> gurligebis   -> no reply yet

I thought gurli was also retired.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-01  1:35 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27  4:18 [gentoo-dev] Marking bugs for bugday? Sebastian Pipping
2010-02-27 15:39 ` Roy Bamford
2010-02-27 17:42   ` Sebastian Pipping
2010-02-27 16:22 ` Mark Loeser
2010-02-27 17:38   ` Sebastian Pipping
2010-02-27 18:14     ` Roy Bamford
2010-02-27 20:15       ` Sebastian Pipping
2010-02-27 20:46         ` Dale
2010-02-27 20:48       ` Mark Loeser
2010-02-27 21:45         ` Ben de Groot
2010-02-27 23:14           ` Mark Loeser
2010-02-28  9:36             ` Dawid Węgliński
2010-02-28 13:15     ` Alexander Færøy
2010-02-28  0:22 ` [gentoo-dev] " Ryan Hill
2010-02-28 19:54 ` [gentoo-dev] " Markos Chandras
2010-02-28 20:04   ` Sebastian Pipping
2010-03-01  1:35     ` Joshua Saddler [this message]
2010-03-01 21:17       ` Ioannis Aslanidis
2010-03-01 22:19         ` Ben de Groot
2010-03-01 22:26           ` Ioannis Aslanidis
2010-03-02  0:02             ` Sebastian Pipping
2010-03-02  0:15               ` Ioannis Aslanidis
2010-03-02  1:09               ` [gentoo-dev] " Duncan
2010-03-02  1:32                 ` Alec Warner
2010-03-02 19:09                   ` Sebastian Pipping
2010-03-02 19:08                 ` Sebastian Pipping
2010-03-02 19:17                   ` Ulrich Mueller
2010-03-02 19:28                     ` Nathan Zachary
2010-03-02 19:39                       ` Sebastian Pipping
2010-03-02 19:42                         ` Nathan Zachary
2010-03-06 14:45                         ` Robert Buchholz
2010-03-06 15:26                           ` Ioannis Aslanidis
2010-03-06 19:09                             ` David Leverton
2010-03-06 20:22                               ` Ioannis Aslanidis
2010-03-07  4:30                               ` Sebastian Pipping
2010-03-07 12:23                                 ` David Leverton
2010-03-08  3:19                               ` Ryan Hill
2010-03-01 22:46           ` [gentoo-dev] " George Prowse
2010-03-01 22:48         ` Mark Loeser
2010-03-02 19:36         ` Sebastian Pipping
2010-03-02 20:47           ` Alec Warner
2010-03-02 21:05             ` Sebastian Pipping
2010-03-02 21:28               ` Alec Warner
2010-03-02 20:59           ` Ioannis Aslanidis
2010-03-04 19:13         ` Roy Bamford

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=20100228173504.78eea0b1@angelstorm \
    --to=nightmorph@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