From: Brian Jackson <iggy@theiggy.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: "François Revol" <revol@free.fr>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: IRC channel movement -> FreeNode to OFTC
Date: Tue, 25 Jan 2011 14:05:32 -0600 [thread overview]
Message-ID: <4D3F2D0C.2020902@theiggy.com> (raw)
In-Reply-To: <AANLkTi=C334Fg_4a5ND3VuEheRLb6HE_iSQ8QLWG7QJd@mail.gmail.com>
On 1/24/2011 1:13 PM, Mike Frysinger wrote:
> On Thu, Dec 9, 2010 at 17:44, Brian Jackson wrote:
>> A. Must be registered to talk in a channel
> i'm fairly certain that is a per-channel setting
But none of the current developers have access to the channel to change
the setting and it's on by default...
>> C. They have strange rules about groups and channel ownership
> ive never had a problem
Yeah, this was a bit vague. I think the biggest issue is that nobody
that's actually involved in qemu currently has any ability to do
anything with the #qemu@freenode. So it's either make a
#therealqemu@freenode, try to convince freenode that the current
developers should have access, or move to a network that is friendlier
to it's users. Guess which one is easiest?
>> D. Their non-profit status in the US was terminated for failure to file
>> paperwork properly
> not terribly relevant if the network continues to function ... just
> dont give them money
> -mike
>
If nobody gives them money how are they going to continue operating?
next prev parent reply other threads:[~2011-01-25 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101209133635.4780834A3D@zimbra14-e2.priv.proxad.net>
2010-12-09 14:06 ` [Qemu-devel] Re: IRC channel movement -> FreeNode to OFTC François Revol
2010-12-09 22:44 ` Brian Jackson
2011-01-24 19:13 ` Mike Frysinger
2011-01-24 19:16 ` François Revol
2011-01-25 20:05 ` Brian Jackson [this message]
2011-01-25 22:24 ` Mike Frysinger
2011-01-25 22:40 ` Brian Jackson
2011-01-25 23:22 ` François Revol
2011-01-25 23:22 ` François Revol
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=4D3F2D0C.2020902@theiggy.com \
--to=iggy@theiggy.com \
--cc=qemu-devel@nongnu.org \
--cc=revol@free.fr \
--cc=vapier.adi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.