linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sekhar Nori <nsekhar@ti.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: old trees
Date: Tue, 17 Sep 2013 16:44:32 +0530	[thread overview]
Message-ID: <52383998.6080504@ti.com> (raw)
In-Reply-To: <20130917170124.0afa2e103a9977355ad7c72c@canb.auug.org.au>

Hi Stephen,

On Tuesday 17 September 2013 12:31 PM, Stephen Rothwell wrote:
> Hi all,
> 
> This message is bcc'd to each of the contacts for the trees listed below,
> so apologies if you get two copies.
> 
> I have been inspired to check the ages of the trees included in
> linux-next.  Below I have listed all the trees that have not been
> commited to in the past 6 months.  Please let me know if the tree is not
> longer in use.  I don't mind keeping these trees in linux-next if they
> will have continued use, but would like to remove any that are no longer
> needed.
> 
> Tree		Last commit
> ----		-----------

> davinci		2 years, 2 months ago

You can remove the davinci tree from linux-next since the patches are
now reaching linux-next through ARM-SoC tree. Apologies for not asking
you to remove it for so long.

Regards,
Sekhar

  reply	other threads:[~2013-09-17 11:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  7:01 linux-next: old trees Stephen Rothwell
2013-09-17 11:14 ` Sekhar Nori [this message]
2013-09-17 23:09   ` Stephen Rothwell
2013-09-17 12:53 ` Josh Boyer
2013-09-17 23:11   ` Stephen Rothwell
2013-09-17 15:36 ` Arnd Bergmann
2013-09-20 18:35 ` Konrad Rzeszutek Wilk
2013-09-23  0:02   ` Stephen Rothwell
2013-09-25 13:27 ` Jonathan Corbet
2013-09-25 23:46   ` 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=52383998.6080504@ti.com \
    --to=nsekhar@ti.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).