linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bgat@billgatliff.com (Bill Gatliff)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Mailing lists have moved
Date: Fri, 21 Aug 2009 10:40:45 -0500	[thread overview]
Message-ID: <4A8EBFFD.5000307@billgatliff.com> (raw)
In-Reply-To: <1250868957.3311.110.camel@macbook.infradead.org>

David Woodhouse wrote:
> On Fri, 2009-08-21 at 09:27 -0600, Paul Walmsley wrote:
>   
>>     
>>> Russell no longer wants to maintain the mailing lists, so with his
>>> blessing I have set up replacements at lists.infradead.org.
>>>       
>> Can you help us understand why the existing linux-arm at vger.kernel.org
>> list is not used for this?
>>     
>
> Russell didn't want to do that, so I offered an alternative solution
> preserving the three separate lists (l-a, l-a-kernel, l-a-toolchain).
>   

Ok, so which of the new lists should former linux-arm-kernel subscribers 
be subscribed to?  I'm confused, I've seen mention of four different 
lists now: three at infraded, and one at vger.  :)


b.g.

-- 
Bill Gatliff
bgat at billgatliff.com

  reply	other threads:[~2009-08-21 15:40 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 11:52 [PATCH] ARM: Mailing lists have moved David Woodhouse
2009-08-21 12:41 ` David John
2009-08-21 13:13 ` Arnd Bergmann
2009-08-21 13:40   ` Alexander Clouter
2009-08-21 13:43     ` Arnd Bergmann
2009-08-21 13:53       ` Alexander Clouter
2009-08-21 16:31         ` David Woodhouse
2009-08-22 21:25       ` Ian Key
2009-08-21 15:20   ` David Woodhouse
2009-08-21 15:28     ` Mark Brown
2009-08-21 15:30     ` Joe Perches
2009-08-21 15:31     ` Arnd Bergmann
2009-08-21 16:02       ` David Woodhouse
2009-08-21 15:27 ` Paul Walmsley
2009-08-21 15:35   ` David Woodhouse
2009-08-21 15:40     ` Bill Gatliff [this message]
2009-08-21 15:46       ` Catalin Marinas
2009-08-21 16:03       ` Bartlomiej Zolnierkiewicz
2009-08-21 16:09       ` David Woodhouse
2009-08-21 16:12         ` Bill Gatliff
2009-08-21 16:14           ` Catalin Marinas
2009-08-21 16:33           ` David Woodhouse
2009-08-21 16:44             ` Paul Walmsley
2009-08-21 17:05             ` Joe Perches
2009-08-21 17:22               ` David Woodhouse
2009-08-21 18:06             ` Theodore Tso
2009-08-21 21:46           ` Sam Ravnborg
2009-08-21 22:03           ` Ben Dooks
2009-08-22  9:20             ` Mark Brown
2009-08-22 12:35               ` Wan ZongShun
2009-08-21 15:56     ` David John
2009-08-21 21:59 ` Ben Dooks
2009-08-24  7:35 ` Riku Voipio
2009-08-24  8:02   ` David Woodhouse
2009-08-24  8:32     ` Pavel Machek
2009-08-24  9:35       ` David Woodhouse
2009-08-31  7:22         ` Eric Miao
2009-08-31  7:45           ` Daniel Stenberg
2009-08-31  7:50             ` Eric Miao
2009-08-31  8:08               ` David Woodhouse
2009-08-31  7:49           ` Karl Hiramoto
2009-08-31  7:56           ` Stefan Schmidt
2009-08-31  7:52             ` Eric Miao
2009-08-31 17:21               ` Mark Brown
2009-08-31  8:05           ` David Woodhouse
2009-08-31 18:33             ` Wolfgang Denk
2009-08-31 18:46               ` David Woodhouse
2009-08-31 19:08                 ` Wolfgang Denk
2009-08-25 12:21 ` Pavel Machek

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=4A8EBFFD.5000307@billgatliff.com \
    --to=bgat@billgatliff.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).