Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!

[Geert Uytterhoeven <geert@linux-m68k.org>]

Hi Mark,

On Wed, Jun 5, 2019 at 11:27 AM Mark Brown <broonie@kernel.org> wrote:
> On Tue, Jun 04, 2019 at 11:16:17AM -0600, Shuah Khan wrote:
> > - Create a directory under our source tree for bugs. This way bugs
> >   stay with the source and we manage them the same way we handle
> >   non-runtime objects: Documenation, scripts etc. This can be flat
> >   directory or have a sub-dir structure underneath.
> >
> >   ../bugs similar to ../Documentation
>
> If bugs are tracked in the source tree doesn't that make it difficult
> for people to update the bugs?

Indeed. While storing the bug state with the sources sounds like a
great idea, it's far from trivial in distributed development:
  - Where are bugs reported (added to git)?
    In upstream, or in maintainer repos?
    At least the tree where a fix is applied should carry the bug report.
  - Unless downstream trees merge from upstream on a regular basis,
    they won't have all reports for bugs that apply to their trees.

Closing bugs does follow the expected path, though: both fix and bug
report update move upstream through a pull request.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds