Hi,
on my behalf, also: thanks to Jonatan!
I could have done this by myself but I was never really sure, which patches I should mark 'superseded' and which not. What rules can I follow? Exactly *when* can I mark a patch this way?
Best, Matthias
On 29.11.2016 16:32, Michael Tremer wrote:
Hi,
just as a reminder, I would like to say that I very much support this.
Patchwork is not "just another project" were the patches are and should rot. It is supposed to help us keeping things tidy and have a clue about what has been submitted and reviewed by whom.
Thank you Jonatan for going through this and cleaning up after us all. I dearly hope that we will be able to keep this tidier from now on.
Best, -Michael
On Wed, 2016-11-09 at 15:27 +0100, Jonatan Schlag wrote:
Hi, some members of this list got or will get some emails from our patchwork and maybe wonder why the patches were superseded. I will try to explain why these emails were sent out. I updated some (i think around 20 to 30) patches, because
- the version in git is newer than the version of the the patch or
- there is a new version of this patch or
- the patch was not correctly caught from the mail (There were 2 patches this
happen) and so the patch was more than one time in patchwork or
- the patch belong to dnsmasq
Regards Jonatan