On Thu, 2011-09-15 at 10:52 +0200, Dodji Seketeli wrote:
> > the above help string might then just suggest that I would rather define
> > my own --enable-maintainer-mode when I want to cover more things under
> > it.
>
> If you do so, please don't call it --enable-maintainer-mode. I agree
> with Ross here. This is an option with confusing enough semantics, so
> please don't overload it more than it ought to.
Hi,
yup, I will not. I realized I wrote a nonsense after I read Javier's
post with --enable-strict bug. That makes much more sense, than what I
was "proposing" here with the --enable-maintainer-mode overload.
Still, after this change, users may change their habit of not passing
--enable-maintainer-mode to use --disable-maintainer-mode on affected
projects, which would be, at least for me, quite surprising change. But
maybe I'm just not an average user after all ;)
Bye,
Milan
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
