On Mon, 17 Jul 2023 18:04:51 +0200 Thomas Monjalon <tho...@monjalon.net> wrote:
> 17/07/2023 16:12, Bruce Richardson: > > On Mon, Jul 03, 2023 at 03:10:57PM -0700, Stephen Hemminger wrote: > > > While going through the old patches, noticed some that are in parts > > > of DPDK that are pretty much abandoned. > > > > > > My suggestion would be introduce a subsystem status field in MAINTAINERS > > > similar to what is done in Linux kernel. > > > > > > S: *Status*, one of the following: > > > Supported: Someone is actually paid to look after this. > > > Maintained: Someone actually looks after it. > > > Odd Fixes: It has a maintainer but they don't have time to do > > > much other than throw the odd patch in. See below.. > > > Orphan: No current maintainer [but maybe you could take the > > > role as you write your new code]. > > > Obsolete: Old code. Something tagged obsolete generally means > > > it has been replaced by a better system and you > > > should be using that. > > > > That seems a useful addition. +1 to add the extra info. > > I think we prefer removing unmaintained code. I would prefer removal as well, but there are things like KNI and that stay around for a year. And marking it as obsolete before removal would help. There are also some marginally useful things like ethtool which no one is maintaining.
