All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.sourceforge.net, olafBuddenhagen@gmx.net
Subject: Re: Move lists to freedesktop.org?
Date: Sat, 06 Mar 2010 01:18:47 +0100	[thread overview]
Message-ID: <1267834727.3849.7971.camel@thor.local> (raw)
In-Reply-To: <20100305161102.6e8c8c8b@jbarnes-piketon>

On Fri, 2010-03-05 at 16:11 -0800, Jesse Barnes wrote: 
> On Fri, 5 Mar 2010 23:19:13 +0100
> <olafBuddenhagen@gmx.net> wrote:
> 
> > Hi,
> > 
> > On Thu, Mar 04, 2010 at 12:37:23PM -0800, Jesse Barnes wrote:
> > 
> > > Would anyone have objections if these lists moved to freedesktop.org?
> > > The recent thread with Linus about the drm pull request highlights the
> > > post lag and non-subscriber aspect of the current lists,
> > 
> > Err, how would moving the list to fdo help with the "non-subscriber
> > aspect"?...
> 
> I was thinking that managing the moderation queue would be faster;
> sf.net is always horribly slow for me, but fdo is usually pretty quick.

Can't say I've really noticed any difference, probably thanks to the
awesome listadmin tool. But it certainly won't hurt.


-- 
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

  reply	other threads:[~2010-03-06  0:18 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 20:37 Move lists to freedesktop.org? Jesse Barnes
2010-03-04 21:38 ` Matt Turner
2010-03-04 21:41 ` Mike Stroyan
2010-03-04 22:14 ` Alex Deucher
2010-03-04 22:42 ` [Mesa3d-dev] " Eric Anholt
2010-03-04 22:55   ` Dan Nicholson
2010-03-04 23:06     ` Jesse Barnes
2010-03-04 23:09 ` Brian Paul
2010-03-04 23:16   ` [Mesa3d-dev] " Michel Dänzer
2010-03-04 23:20     ` Jesse Barnes
2010-03-23 19:32       ` Jesse Barnes
2010-03-23 22:21         ` Michel Dänzer
2010-03-24  2:53         ` sean darcy
2010-03-04 23:17   ` Stephane Marchesin
2010-03-05 22:19 ` olafBuddenhagen
2010-03-06  0:11   ` Jesse Barnes
2010-03-06  0:18     ` Michel Dänzer [this message]
2010-03-10 16:36 ` James Simmons
2010-04-08 22:21   ` Brian Paul
2010-04-08 22:38     ` Alex Deucher
2010-04-08 23:37       ` Jesse Barnes
2010-04-09  0:07         ` Stephane Marchesin
2010-04-14  0:08         ` [Mesa3d-dev] " Matthew W. S. Bell
2010-04-14 20:52           ` Brian Paul
     [not found]           ` <4BC62AFF.40804@vmware.com>
2010-04-14 21:09             ` Dan Nicholson
2010-04-14 21:16               ` Brian Paul
     [not found]               ` <4BC6309E.1030701@vmware.com>
2010-04-15  9:12                 ` [Mesa-dev] " Tormod Volden

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=1267834727.3849.7971.camel@thor.local \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=olafBuddenhagen@gmx.net \
    /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.