Hi David, On 2012-02-22 22:15, David Prévot wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 user www.debian.org@packages.debian.org usertag 660950 content misc severity 660950 minor thanks Hi Filipus, Le 22/02/2012 22:39, Filipus Klutiero a écrit :The Awards page entry of April 2006 about Linux+ links to http://www.lpmagazine.org/fr which yields a 404 error.It seems that you totally missed Simon's point yesterday, so let me try to offer you some subtitles. Le 22/02/2012 18:27, Filipus Klutiero a écrit :On 2012-02-21 15:46, Simon Paillard wrote:On Tue, Feb 21, 2012 at 03:26:04PM -0500, Filipus Klutiero wrote: Do you know that, for such trivial change: - you could avoid the overhead of BTS ?Hum, overhead when compared to what?Compared to sending a simple mail to debian-www@l.d.o…
I'm aware that I could send a mail to debian-www. If that's what Simon meant though, I don't see much overhead in using the BTS instead...
- send a patch against cvs ?I do know that I could send a patch ...So please, do it!
Sorry, my reply was an understatement. To be clear, I consider it inefficient to send patches for trivial issues of the kind.
but I also know that wouldn't be very efficient for trivial problems of this kind.It would be far more efficient to review and apply a simple patch.
To clarify, I was talking about the efficiency of the process as a whole, not just about applying the fix.
A patch would make a lot more clear what the issue actually is, and since you already thought about it, the fix you propose. Reading a certain amount of lines that doesn't always totally make sense is not the most efficient way to communicate for trivial problems of this kind…
While a patch might clarify an issue, I'm afraid it wouldn't add much clarity to issues like this one. If you can't understand such issues, I recommend you leave someone else address them.
Of course, feel free to request explanations.
[...]
In other words, Filipus, please provide patches for trivial problems directly to debian-www@l.d.o.
Sorry, that doesn't scale. I can't track the status of each of my reports to various mailing lists this way.
Once we've witnessed that you're actually able to offer something useful, we'd be happy to grant you commit access so you can fix them directly. Regards David