linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: antoine.tenart@bootlin.com (Antoine Tenart)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: please clean up the alpine tree
Date: Fri, 23 Mar 2018 09:51:53 +0100	[thread overview]
Message-ID: <20180323085153.GB9682@kwain> (raw)
In-Reply-To: <20180323083315.58976d73@canb.auug.org.au>

Hi Stephen,

On Fri, Mar 23, 2018 at 08:33:15AM +1100, Stephen Rothwell wrote:
> 
> The alpine tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/atenart/linux.git#alpine/for-next)
> only contains commits that have been upstreamed as different commits.
> It also hasn't been updated since late March 2017.  Please clean it up
> (it takes some time to merge - presumably just because of its age).
> 
> Or, if it is no longer being used, please let me know and I will remove
> it from linux-next.

Thanks for pointing this out, and sorry for the inconvenience. The
Alpine tree isn't very active and I haven't got patches for quite
some time.

I updated alpine/next to point to v4.16-rc1 to fix the issue. It's not
completely dead, but as it's not active you can also remove the
alpine/for-next tree from linux-next. And when/if I get patches to merge
in the future I'll ask to add it back. As you wish :)

Thank you for making linux-next!
Antoine

-- 
Antoine T?nart, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-03-23  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 21:33 linux-next: please clean up the alpine tree Stephen Rothwell
2018-03-23  8:51 ` Antoine Tenart [this message]

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=20180323085153.GB9682@kwain \
    --to=antoine.tenart@bootlin.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).