+1 My only real objection to Ryan making that commit is that I specifically chose to not make it 'openmaintainer' so that I at least get a ping before anyone makes any changes. The existing policy only has an escape for that in the case of something being broken (not building, security fix) in which case I usually would expect either a ping anyway or a commit from someone + a ping letting me know what they did and why.
Having a policy for obvious fixes seems like a good option too. In any case, I would have appreciated a note from Ryan about it. On Jan 11, 2013, at 11:12 AM, Blair Zajac <[email protected]> wrote: > We should have an obvious fix rule: > > http://subversion.apache.org/docs/community-guide/roles.html#obvious-fix > > Blair > > On 01/11/2013 02:05 AM, Ryan Schmidt wrote: >> Pardon; I didn't think there would be any objection to fixing this obvious >> error in the previous commit. >> >> On Jan 11, 2013, at 02:57, "Daniel J. Luke" <[email protected]> wrote: >> >>> subversion isn't an openmaintainer port, and this doesn't fix a broken >>> build issue as far as I'm aware... -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
