linux-kernel - Re: [PATCH] staging: lustre: update the TODO list

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] [day] [month] [year] [list]

Date:   Sun, 11 Feb 2018 19:21:06 -0800
From:   Joe Perches <joe@...ches.com>
To:     James Simmons <jsimmons@...radead.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        devel@...verdev.osuosl.org,
        Andreas Dilger <andreas.dilger@...el.com>,
        Oleg Drokin <oleg.drokin@...el.com>,
        NeilBrown <neilb@...e.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Lustre Development List <lustre-devel@...ts.lustre.org>
Subject: Re: [PATCH] staging: lustre: update the TODO list

On Mon, 2018-02-12 at 02:06 +0000, James Simmons wrote:
> > On Sun, 2018-02-11 at 18:00 -0500, James Simmons wrote:
> > > As more people become involved with the progression of the lustre
> > > client it needs to more clear what needs to be done to leave
> > > staging. Update the TODO list with the various bugs and changes
> > > to accomplish this. Some are simple bugs and others are far more
> > > complex task that will change many lines of code. Some even cover
> > > updating the user land utilities to meet the kernel requirements.
> > > Several bugs have already been addressed and just need to be
> > > pushed to the staging tree.
> > 
> > Nice list.
> 
> Thanks. Its nice to have a direction :-)
> 
> > Are or should those entries that have been addressed
> > also in this new list?
> 
> Do you mean by those entries what originally was in the
> TODO list or what has been fixed over the last 2 years?

My reading of

> Several bugs have already been addressed and just need to be
> pushed to the staging tree.

is that the new list contains entries for things
that have already been fixed but have not yet
been pushed to the staging tree.

So, if there are entries in the new TODO list
that really are fixed, but not yet posted, then
marking those entries as TODO seems inappropriate.