linux-kernel - Re: linux-next: tidy up of trees

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Jan 2015 08:37:39 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	<linux-next@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: tidy up of trees

On Wed, 21 Jan 2015 15:10:09 +1100
Stephen Rothwell <sfr@...b.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/