Daniel Axtens <d...@axtens.net> writes: > Stephen Finucane <step...@that.guru> writes: > >> On Thu, 2018-01-25 at 16:21 +1100, Daniel Axtens wrote: >>> Hi Stephen, >>> >>> This is a good idea and I'm happy for it to go in as-is, before the >>> rest >>> of the series. >>> >>> Reviewed-by: Daniel Axtens <d...@axtens.net> >> >> I've been thinking a little more on this and I don't know if I actually >> want to do this. If we manage to solve the performance impact, we can >> use events as an auditor and display things like state changes on the >> patch detail page. I might leave this one for another while. Would >> still appreciate reviews on the rest of this series though. > > I think having this configurable would be the best. Perhaps have > 0 = disable, 1+ = delete after N days. > > (Maybe we need to expose a unique ID for patches to help people who use > them.) As it turns out, we already do this.
> > Regards, > Daniel > >> >> Stephen >> >>> >>> Regards, >>> Daniel _______________________________________________ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork
