linux-kernel - Re: linux-next: trees being removed

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]

Message-ID: <06bc4404-ec60-4f38-a568-6600969f6f96@kernel.org>
Date: Wed, 19 Feb 2025 11:58:58 -0800
From: Vineet Gupta <vgupta@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Vineet Gupta <vgupta@...nel.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Dan Williams <dan.j.williams@...el.com>,
 "Gustavo A. R. Silva" <gustavo@...eddedor.com>,
 Jeff Layton <jlayton@...nel.org>, Jeremy Kerr <jk@...abs.org>,
 Joel Stanley <joel@....id.au>, Kent Overstreet <kent.overstreet@...ux.dev>,
 Linus Walleij <linus.walleij@...aro.org>, Nick Terrell <terrelln@...com>
Subject: Re: linux-next: trees being removed

On 2/16/25 03:11, Stephen Rothwell wrote:
> Hi Vineet,
>
> On Wed, 12 Feb 2025 22:02:09 +0530 Vineet Gupta <vgupta@...nel.org> wrote:
>> On 2/12/25 04:26, Stephen Rothwell wrote:
>>> The following trees are going to be removed from linux-next because they
>>> have not been updated in more than a year.  If you want a tree restored,
>>> just let me know (and update its branch).
>>>
>>> Tree			Last commit date
>>>   URL
>>>   comits (if any)
>>> ----			----------------
>>> arc			2023-09-10 16:28:41 -0700
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-next  
>> Ack: We don't need 2 next tending trees for ARC any longer.
> This is supposed to be the development tree.  The only other one I have
> is arc-current
> (git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git#for-curr)
> which is for bug fixes.  So do you really not do any development any more?

For quite some time I've been using just # for-curr for both fixes/features, as
dev as slowed down.
Things might change if and when work picks up on ARCv3/arc64 bit for now
for-curr suffices.

Thx,
-Vineet