From: Hank Leininger <hlein@marc.info>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@linaro.org>,
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 16:50:17 -0400 [thread overview]
Message-ID: <20130720205017.GC1877@marklar.spinoli.org> (raw)
In-Reply-To: <CACxGe6v=sKb7acuEB3__sxdeq_7hnMLnwJxfPwiLxSPMfgo1oQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Sat, Jul 20, 2013 at 08:18:54PM +0100, Grant Likely wrote:
> On Sat, Jul 20, 2013 at 6:00 PM, Hank Leininger <hlein@marc.info> wrote:
> >
> > 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)?
>
> As long as it doesn't cause any problems with duplicate messages for
> the next short little while, I would merge the two archives.
Sold! Importing them now as 'devicetree'. Because I grabbed them at
the same time as I subscribed to the new list, there shouldn't be any
overlap/duplicates.
Thanks,
Hank
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 447 bytes --]
next prev parent reply other threads:[~2013-07-20 20:50 UTC|newest]
Thread overview: 8+ 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:29 ` Joe Perches
2013-07-20 16:28 ` Linus Walleij
2013-07-20 17:00 ` Hank Leininger
[not found] ` <20130720170047.GB1877-+o3RUvwP9FWmwd5QzNGvFEB+6BGkLq7r@public.gmane.org>
2013-07-20 19:18 ` Grant Likely
2013-07-20 20:50 ` Hank Leininger [this message]
2013-07-24 19:25 ` Grant Likely
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=20130720205017.GC1877@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 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).