On 10/18/2016 09:41 PM, Boris Brezillon wrote:
>> Patchwork is nice, it helps keeping track of the patch status real well.
>> But there is always the problem of keeping the patchwork up-to-date when
>> the status of patch changes, esp. if one is offline (or maybe I didn't
>> look hard enough).
> I use git notes + a pre-push hook to help mark a patch as 'Accepted' in
> patchwork, but still, it does not automate moving patches to the
> 'Superseeded' state (which IMO should be directly handled in patchwork)
> and those who are rejected. This is why the backlog tend to grow until
> I decide to do some cleanup.
> We also have all those patches which are over 1 year old, but that we
> keep just in case someone wants to revive them.
> Anyway, I think patchwork is very useful if it's well maintained, so
> maybe we should cleanup things after each release.
You've very much nailed it. Those are all my complaints about patchwork
and problems we had in U-Boot. Cleaning it up took a while.
One just has to keep an eye on patchwork so it doesn't get out of
control, otherwise the mountain of patches you have no clue about
anymore becomes the source of utter frustration.
>>> I think Boris and I have been sort of
>>> using it, but it's still got a pretty good backlog (partly real --
>>> i.e., the cause for this thread; and partly artificial, due to
>>> What to do about mtd-utils.git? That's been languishing a bit, and it
>>> has no release schedule. Maybe we want a plan for that too.
>>> BTW, will anybody be at Linux Plumbers? I plan to be there in a few
>>> weeks. And something tells me dwmw2 will be there.