On 02/25/2018 07:41 AM, Dibyendu Majumdar wrote: > On 25 February 2018 at 13:45, Christopher Li <sparse@xxxxxxxxxxx> wrote: >> On Sun, Feb 25, 2018 at 4:51 AM, Dibyendu Majumdar >> <mobile@xxxxxxxxxxxxxxx> wrote: >>> Is it worth reintroducing sparse-next where more 'in-progress' changes >>> are done? This will allow 'master' to be only for bug fixes or >>> emergency fixes. >> >> Either way is fine with me. >> > > If you agree then maybe the fix for PSEUDO value size should be moved > to sparse-next? That way, folks wanting bug fixes can go to master, > and not have to deal with 'in-progress' work. > >>> I would also suggest having a way of tracking change / bug fix >>> requests. Perhaps a Github mirror repository can be used just for this >>> - i.e. use the issue tracker to help users raise bugs, and also allow >>> users to vote on fixes or changes. I have seen some other projects >>> doing this - i.e. the code in Github is simply a mirror, but issue >>> tracker is used as a way of managing changes. >> >> There is also a bugzilla at kernel.org for consideration. >> > > Cool. I don't see a Component defined for Sparse there - can one be > created under Tools perhaps? > I am happy to raise bugs there for all the issues I have found. We can certainly request that to the admin(s) if that is the choice here. It should be do-able (he says with no admin knowledge -- I'm just a user there). We (me, I guess Josh, other people) know how to contact the admin(s) and make such a request. -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
