On Wed, Dec 05, 2007 at 05:40:59AM -0800, J.C. Roberts wrote:
> You are advocating talk rather than code.
No. He is asking you to stop wasting people's time.
> Your accusation of not caring about the actual changes to the
> ports is completely unfounded. I've been very carefully walking
> the dependency trees, updating all dependencies before updating
> the parent.
Are you testing all dependencies when you update a given port? Are
you testing the updates at all?
[...]
> Talking to a maintainer first is rude, pushy and manipulative
> because it is tantamount to asking the maintainer to do an update
> and to take their responsibility more seriously --it's a guilt
> trip.
No, it's not. When you update a port, send the diff with a note to
the maintainer. They'll review the change, maybe modify it, and then
pass it up the chain for submission. If you don't hear back from
them, mail ports@ after a reasonable period of time. This is how
things work here.
This process ensures that diffs get a review from people who are
responsible for the relevant code. It also helps actual ports
devs triage. Instead of wading through a deluge of possibly untested
and unreviewed patches (like those you've sent), committers can
(hopefully) trust that a maintainer's done their job.
> I do not expect *you* to spend your free time doing the work that
> *I* want done. I just do the work myself, and share the results.
Make diffs -- that's great. But send them to the maintainer first
for review before spamming the list. You'll have noticed by now that
the diffs you've sent haven't gone very far. If you really want to
improve things, stick to the process and the ports tree will
improve. If you continue to spam the list, you'll only slow real
progress down, and that sucks.
(IANAD)
--
o--------------------------{ Will Maier }--------------------------o
| web:.......http://www.lfod.us/ | [EMAIL PROTECTED] |
*------------------[ BSD Unix: Live Free or Die ]------------------*
