From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
Josh Boyer <jwboyer@gmail.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: no tree for Sept 6
Date: Wed, 21 Sep 2011 22:54:12 -0300 [thread overview]
Message-ID: <4E7A9544.9040006@infradead.org> (raw)
In-Reply-To: <20110911141958.8e404c8b943af1c73886cee5@canb.auug.org.au>
Em 11-09-2011 01:19, Stephen Rothwell escreveu:
> Hi Mauro,
>
> On Wed, 07 Sep 2011 11:08:53 -0300 Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
>>
>> It seems that we need a backup plan. In my case, I could put the tree
>> for -next at infradead or at linuxtv, but that means to re-configure
>> everything at Stephen's side.
>
> That is not a big issue at all. If you wish to move your tree, just let
> me know (preferably in a public manner to raise my confidence in its
> provenance - I am a bit more paranoid, now :-)).
Hi Stephen,
Please replace my media tree (v4l-dvb) by this one:
git://linuxtv.org/mchehab/media-next.git
I'll set soon a new tree for my edac patches as well.
Thank you!
Mauro
next prev parent reply other threads:[~2011-09-22 1:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 6:40 linux-next: no tree for Sept 6 Stephen Rothwell
2011-09-06 17:17 ` Arnaud Lacombe
2011-09-06 17:23 ` Josh Boyer
2011-09-06 17:29 ` Arnaud Lacombe
2011-09-06 17:37 ` Randy Dunlap
2011-09-06 18:18 ` Josh Boyer
2011-09-06 18:30 ` Arnaud Lacombe
2011-09-07 14:08 ` Mauro Carvalho Chehab
2011-09-11 4:19 ` Stephen Rothwell
2011-09-22 1:54 ` Mauro Carvalho Chehab [this message]
2011-09-22 2:23 ` Stephen Rothwell
2011-09-22 2:48 ` Mauro Carvalho Chehab
2011-09-22 14:26 ` Stephen Rothwell
2011-09-22 17:48 ` Mauro Carvalho Chehab
2011-09-07 7:16 ` Stephen Rothwell
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=4E7A9544.9040006@infradead.org \
--to=mchehab@infradead.org \
--cc=jwboyer@gmail.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.