All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] List fault?
Date: Wed, 04 May 2011 18:06:25 +0000	[thread overview]
Message-ID: <4DC195A1.3020906@riverviewtech.net> (raw)
In-Reply-To: <4DC0791D.903@bowenvale.co.nz>

On 05/04/11 12:03, Radu Oprisan wrote:
> I can set-up another mailing list in the morning (8 PM now, EEST).
>  Think we can get somebody else to join?

I'm not opposed to a new mailing list in and of its self.

However I think that this list (LARTC) is well known and documented all 
over the place.  So even if we migrate elsewhere, there will still be 
people that stumble on to this list.

I've personally noticed, for the last couple of years, that this list 
would be *EXTREMELY* delayed (as in weeks to months) for some unknown 
reason.  -  As I look at headers of some of the recent messages, I see 
that a message sat in the queue on the server for multiple months before 
being delivered to my mail server.

Seeing that now messages seem to be flowing in a timely manner, I'd 
suggest that we give this list a week to a month probation to see if it 
has straightened up it's act.

I'd also like a comment from the list maintainer or a moderator in his / 
her stead.

Other than the above concern, I'll support moving to a new mailing list 
as long as there are messages to this list (so that they can be found in 
archives) indicating the move.



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2011-05-04 18:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 21:52 [LARTC] List fault? Don Gould
2011-05-04  3:43 ` Andreas Unterkircher
2011-05-04  6:04 ` Andrew Beverley
2011-05-04  6:15 ` Nikolay Kichukov
2011-05-04  6:26 ` Kim Bak
2011-05-04 12:35 ` Vitaly Tskhovrebov
2011-05-04 12:50 ` Andy Fletcher
2011-05-04 13:02 ` João Almeida
2011-05-04 16:56 ` Radu Oprisan
2011-05-04 17:02 ` Brent Clark
2011-05-04 17:03 ` Radu Oprisan
2011-05-04 18:06 ` Grant Taylor [this message]
2011-05-04 18:37 ` Radu Oprisan
2011-05-04 19:11 ` Gregory Papangeles
2011-05-04 19:11 ` Grant Taylor
2011-05-04 19:24 ` Grant Taylor
2011-05-04 19:24 ` Micro-Shock
2011-05-04 19:33 ` Radoslaw Horodniczy
2011-05-04 19:37 ` David Hough
2011-05-04 19:40 ` Stuart Sheldon
2011-05-04 19:59 ` Radu Oprisan
2011-05-04 19:59 ` Grant Taylor
2011-05-04 20:12 ` Gregory Papangeles
2011-05-04 20:14 ` Javier Charne
2011-05-04 20:15 ` Ruben Rögels
2011-05-04 20:18 ` Ralph Loader
2011-05-04 20:19 ` Victor Julien
2011-05-04 21:56 ` Joe Perches
2011-05-04 23:17 ` Andrew Beverley
2011-05-04 23:18 ` Andrew Beverley
2011-05-04 23:40 ` Russell Stuart
2011-05-04 23:56 ` Alex Samad
2011-05-05  1:23 ` Indra Tjahjono
2011-05-05  2:10 ` Russell Stuart
2011-05-05  4:33 ` Alexander Samad
2011-05-05  5:59 ` Andrew Beverley
2011-05-05  6:23 ` Nikolay Kichukov
2011-05-05 12:44 ` Luciano Ruete
2011-05-05 13:52 ` Andrew Burgess
2011-05-05 15:19 ` João Almeida
2011-05-06  6:39 ` Adrian Moisey
2011-05-06 12:30 ` Yevgeny Kosarzhevsky

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=4DC195A1.3020906@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=lartc@vger.kernel.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 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.