patchwork series bug
Bin Meng
bmeng.cn at gmail.com
Sat Nov 7 01:11:33 AEDT 2020
Hi Lukas,
On Fri, Nov 6, 2020 at 10:03 PM Lukas Bulwahn <lukas.bulwahn at gmail.com> wrote:
>
> On Fri, Nov 6, 2020 at 2:49 PM Daniel Axtens <dja at axtens.net> wrote:
> >
> > Bin Meng <bmeng.cn at gmail.com> writes:
> >
> > > On Wed, Oct 28, 2020 at 1:58 PM Bin Meng <bmeng.cn at gmail.com> wrote:
> > >>
> > >> Hi,
> > >>
> > >> Please see below two series:
> > >>
> > >> Series #1: http://patchwork.ozlabs.org/project/qemu-devel/list/?series=210330
> > >> Series #2: http://patchwork.ozlabs.org/project/qemu-devel/list/?series=210336
> > >>
> > >> The following patch
> > >> http://patchwork.ozlabs.org/project/qemu-devel/patch/20201027141740.18336-7-bmeng.cn@gmail.com/
> > >>
> > >> should really be put in series #2, not series #1.
> > >>
> > >> Not sure why this bug happens, as you can see clearly from the message
> > >> id, the patch should belong to series #2.
> > >
> > > Ping?
> >
>
> Open-source works because when it matters to someone, that someone
> creates a patch that fixes it.
>
> Does that make sense? Does it matter to you, Bin? Then you know what
> needs to be done :)
Makes perfect sense. I just wanted to make sure this report does not
get slipped.
> Daniel and Stephen rescued a useful but (almost) dead project, and
> modernized and resurrected it... now it is the time for more users to
> keep it alive.
I have to admit that I do not know much history about the patchwork
project. I thought it was actively maintained. I need to say that
patchwork is a very helpful tool and a big thanks to all the
developers/maintainers. I was trying to help as a user starting from
reporting bugs :)
Regards,
Bin
More information about the Patchwork
mailing list