public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Roy Marples <roy@marples.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] OpenRC available for testing.
Date: Thu, 03 Jan 2008 10:40:58 +0000	[thread overview]
Message-ID: <1199356858.1574.33.camel@localhost> (raw)
In-Reply-To: <df1735a20801030218q3085e4ebxf8141288be46fe96@mail.gmail.com>

On Thu, 2008-01-03 at 10:18 +0000, Richard Brown wrote:
> While this thread remains highly entertaining, I'm sure as a past
> gentoo developer Roy remembers that we don't generally use gentoo-dev
> to bug fix poorly written makefiles, we have a bugzilla where people
> interested in fixing it can help, or perhaps upstream have a list
> where they can discuss it.

One of the "deals" was that whilst Gentoo would likely use OpenRC it
would still do the hosting. As Gentoo would be using it, it does pertain
to Gentoo development.

So either I host my own bug tracker (which I'm more than happy to do
btw), or Gentoo can get one hosted ASAP. Maybe a mailing list a well
(again, I can host this too).

The next Council meeting is next week, so I'll ask them the status then.

You'll not hear from me again on this list.

> Warmest Regards in the New Year,

Same to you :)

Thanks

Roy

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2008-01-03 10:43 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01 12:41 [gentoo-dev] OpenRC available for testing Roy Marples
2008-01-01 12:45 ` Roy Marples
2008-01-01 13:23   ` Alon Bar-Lev
2008-01-01 15:06     ` Petteri Räty
2008-01-01 16:55       ` Alon Bar-Lev
2008-01-01 17:11         ` Roy Marples
2008-01-01 17:22         ` Alon Bar-Lev
2008-01-01 17:48           ` Roy Marples
2008-01-03  6:43           ` Alon Bar-Lev
2008-01-03  9:46             ` Roy Marples
2008-01-03 10:02               ` Alon Bar-Lev
2008-01-03 10:09                 ` Roy Marples
2008-01-01 19:16 ` Thomas Pani
2008-01-01 19:31   ` TimeBreach
2008-01-01 19:49   ` Roy Marples
2008-01-02 14:39     ` Alon Bar-Lev
2008-01-02 15:05       ` Roy Marples
2008-01-02 15:15         ` Alon Bar-Lev
2008-01-02 15:50           ` Roy Marples
2008-01-03 15:49         ` Mike Frysinger
2008-01-03 18:19           ` Roy Marples
2008-01-06 13:34             ` [gentoo-dev] " Steve Long
2008-01-09 21:26             ` [gentoo-dev] " Mike Frysinger
2008-01-09 21:48               ` Chris Gianelloni
2008-01-09 22:58                 ` Mike Frysinger
2008-01-03 15:50     ` Mike Frysinger
2008-01-03 16:24       ` Roy Marples
2008-01-03 17:58         ` Roy Marples
2008-01-09 21:27           ` Mike Frysinger
2008-01-02 16:52 ` Santiago M. Mola
2008-01-02 17:39   ` Roy Marples
2008-01-03  4:38 ` Nathan Smith
2008-01-03  9:49   ` Roy Marples
     [not found] ` <9e0cf0bf0801030055u3564058fy7f9595d4df86674a@mail.gmail.com>
2008-01-03  8:58   ` Alon Bar-Lev
2008-01-03  9:50     ` Roy Marples
2008-01-03 10:13       ` Roy Marples
2008-01-03 10:18         ` Richard Brown
2008-01-03 10:40           ` Roy Marples [this message]
2008-01-03 12:12             ` Santiago M. Mola
2008-01-06 13:45               ` [gentoo-dev] " Steve Long
2008-01-03 14:01           ` [gentoo-dev] " Wulf C. Krueger
2008-01-09 21:30             ` Mike Frysinger
2008-01-03 23:35           ` Luca Barbato
2008-01-03 11:43       ` Alon Bar-Lev

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=1199356858.1574.33.camel@localhost \
    --to=roy@marples.name \
    --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