From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Wulf C. Krueger" <philantrop@gentoo.org>
Subject: Re: [gentoo-dev] OpenRC available for testing.
Date: Wed, 9 Jan 2008 16:30:28 -0500 [thread overview]
Message-ID: <200801091630.29257.vapier@gentoo.org> (raw)
In-Reply-To: <200801031501.21761.philantrop@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Thursday 03 January 2008, Wulf C. Krueger wrote:
> On Thursday, 03. January 2008 11:18:19 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,
>
> First of all, OpenRC is likely to become an integral part of Gentoo so its
> discussion is most likely on-topic here.
>
> Furthermore, I prefer reading about "poorly written" Makefiles instead of
> poorly written mails, dear Richard.
come guys, lesbie friends. Richard has a point that discussing broken
makefiles generally isnt on topic for the list, but it'd be hard to maintain
separate threads properly (off-list/somewhere else about building, on-list
about conventions/changes/etc...). people miss things and the threads get
fragmented and it's a mess. so please just bear the brunt of the on/off
topic pieces as in the end the winner clearly is us.
> You might want to remember that subscription to his mailinglist is no
> longer mandatory if technical discussions bother you so much.
this really wasnt needed. he had a valid concern. please give up some hugz.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2008-01-09 21:30 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
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 [this message]
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=200801091630.29257.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=philantrop@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