Re: MAINTAINERS in svn -- have it or no commit for you

[Olav Vitters <olav bkor dhs org>]

On Sat, Sep 01, 2007 at 01:20:08PM +0100, Gustavo J. A. M. Carneiro wrote:
> On Sex, 2007-08-31 at 19:55 +0200, Olav Vitters wrote:
> > On Sun, Aug 12, 2007 at 01:55:35AM +0200, Olav Vitters wrote:
> > > On Wed, Aug 08, 2007 at 12:36:28AM +0200, Olav Vitters wrote:
> > > > Note that the userid is really important. Otherwise ensure that the
> > > > E-mail address is the one your @svn.g.o alias forwards to.
> > > 
> > > I've made an pre-commit script which detects if a module has a valid
> > > /trunk/MAINTAINERS file. This currently isn't activated, however I might
> > > do this in future.
> > 
> > This has now been enabled. Means you cannot commit to modules without a
> > proper MAINTAINERS file. The rejection message points to an URL
> > explaining this.
> 
> It is not nice to do this like this; you should make the pre-commit

I've asked everyone to update the files around 3 weeks ago. I've had a
complaint that I should've mailed the maintainers directly, but that is
exactly the problem I'm trying to solve.
I do understand this is heavy handed way of getting that information.

> script give only a warning, for a few months, but still allow commit.
> Only after the warning period should commit be denied.

You cannot generate a warning. Everything printed to stderr is ignored.

-- 
Regards,
Olav