cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: [PATCH][Gump] your definitions break Gump builds
Date Fri, 17 Jun 2005 07:57:54 GMT
Stefano Mazzocchi wrote:
> Stefan Bodewig wrote:
> > On Thu, 16 Jun 2005, Stefano Mazzocchi <stefano@apache.org> wrote:
> > 
> > 
> >>it's not a matter of being annoyed enough (we are already!), it's
> >>the fact that cocoon needs that file at build time.
> > 
> > 
> > Hmm, so why don't you realize that you have a typo in it for many
> > days?  Like when you rename a jar but forget to update the descriptor?
> 
> because cocoon doesn't use *all* of that data, only parts.
> 
> Truth be told, cocoon could have two files, one for gump and one for its
> own build system, but they would contain the same information.
> 
> >>Now, I would be totally in favor of granting the gump committers
> >>commit access to the cocoon project.
> > 
> > Should be quite trivial to add a rule to asf-authorization that grants
> > rw to @gump for just that file, at least I think it allows
> > file-granularity.
> 
> Even better. Can we do it or is it something that infra@ has to do?

PMC chairs can do it.

-David

Mime
View raw message