Le Thu, Aug 06, 2009 at 09:26:02AM -0700, Russ Allbery a écrit : > > (filterdiff comes with patchutils.) Given that, this seems like a tempest > in a teapot to me. Just convert the diff into whatever format the tool > that you're using expects or the reviewer wants to read.
Hi Russ and everybody, I already explained that I prefered that the patch stays in the original format so that it is easy for everybody (co-maintainers, reviewers, users) to verify that it was not altered. Giving a standard interface to reviewers is a laudable goal, but I do not see reviewers except in elaborate scenarios about security. Therefore I will not trade a real benefit for a hypothetical one, even if both are neglectible. Also, I think that it is very important in a project of 1,000 persons to stick to facts, and avoid building illusions together. So as long as there is no reviewing process nor package reviews, there is no need to adapt to imaginary reviewers. This said, if there were a project-wide momentum for standardising on one patch format, I would not oppose. This would probably be a release goal, a preparation for a Policy change, or a demand from the security team to the package manintainers. Something with a motivation, a plan, some facts and some volunteers to get things done. I have reassigned the bug of my package to dpkg-dev. It is holiday season, so let's wait for a while and see the answer of the dpkg developers. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org