mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: <linux-next@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: tidy up of trees
Date: Wed, 21 Jan 2015 08:37:39 -0500	[thread overview]
Message-ID: <20150121083739.1b29cfca@gandalf.local.home> (raw)
In-Reply-To: <20150121151009.0cb88a21@canb.auug.org.au>

On Wed, 21 Jan 2015 15:10:09 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> [affected tree contacts are bcc'd on this email]
> 

> kconfig
> Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-kconfig.git#for-next
> 

This is my localmodconfig repo. I only use it when someone points out
something broke or I find a better way of doing something.

It doesn't get updated much because so far, I hear localmodconfig and
localyesconfig are doing everything that people like. It may not ever
get updated again if everyone (including myself) stays happy with it :-)

But in case that changes, and I need to restructure it, this will be
needed again. Should I just let this go out of next, but I'll probably
forget that it does, and still think my for-next branch is active.

If it is any extra burden on you to keep it, then I'm fine with it
falling off the radar. But if it's just "I have X repos in next, and
I'm trying to make it Y", I'd rather keep it in.

Thanks!

-- Steve

  reply	other threads:[~2015-01-21 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21  4:10 Stephen Rothwell
2015-01-21 13:37 ` Steven Rostedt [this message]
2015-01-21 21:09   ` 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=20150121083739.1b29cfca@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®