All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hank Leininger <hlein@marc.info>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	devicetree@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Joe Perches <joe@perches.com>
Subject: Re: New device tree mailing list
Date: Sat, 20 Jul 2013 13:00:47 -0400	[thread overview]
Message-ID: <20130720170047.GB1877@marklar.spinoli.org> (raw)
In-Reply-To: <CACRpkdZ=THRiyrDqwDR7NT97EpFCT474mjG8_S1_mEM0rJ1oEg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]

On Sat, Jul 20, 2013 at 06:28:19PM +0200, Linus Walleij wrote:
> Hi MARC list archive folks,
> 
> could you please start archiving the following recently addes VGER lists
> at marc.info:
> 
> These go into the "Linux" folder:
> linux-gpio: http://vger.kernel.org/vger-lists.html#linux-gpio
> linux-spi: http://vger.kernel.org/vger-lists.html#linux-spi
> 
> This one goes into "Development" or "Misc" I guess:
> devicetree: http://vger.kernel.org/vger-lists.html#devicetree

Sure, I've just subscribed us to all three.  They'll show in 'Misc' once
some traffic comes in, and then I'll (have to remember to) move them.

I realize MARC didn't carry the old/original devicetree-discuss list at
ozlabs.  I'm pulling down the archives from that list now.  Should I
import them as 'devicetree-discuss' (historically accurate) or as
'devicetree' (so they will appear seamless in MARC w/the new vger list's
traffic)?

AFAIK vger doesn't keep copies of old messages, but if any list-members
have mailspools of past traffic for linux-gpio and/or linux-spi, please
contact me directly and I'll import them.

Thanks,

-- 

Hank Leininger <hlein@marc.info>
3C2A 4EEE ED36 D136 18F2  1B30 47A8 D14B E13E 9C6A

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 447 bytes --]

  reply	other threads:[~2013-07-20 17:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20  1:23 New device tree mailing list Grant Likely
2013-07-20  1:23 ` Grant Likely
2013-07-20  1:29 ` Joe Perches
2013-07-20 16:28   ` Linus Walleij
2013-07-20 16:28     ` Linus Walleij
2013-07-20 17:00     ` Hank Leininger [this message]
     [not found]       ` <20130720170047.GB1877-+o3RUvwP9FWmwd5QzNGvFEB+6BGkLq7r@public.gmane.org>
2013-07-20 19:18         ` Grant Likely
2013-07-20 19:18           ` Grant Likely
2013-07-20 20:50           ` Hank Leininger
2013-07-24 19:25   ` Grant Likely
2013-07-21  3:22 ` [U-Boot] Fwd: " Stephen Warren
2013-07-30 11:51 ` Florian Fainelli

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=20130720170047.GB1877@marklar.spinoli.org \
    --to=hlein@marc.info \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@secretlab.ca \
    --cc=joe@perches.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@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.