I think a safe solution is to put the "patchqueue" build on the apache server, so only a committer can access and run it. But I don't know if there is a infrastructure for it. If we include this build in the CVS anyone could run it - and definitly will.
Carsten David Crossley wrote: > > This is a useful thing to have, this "patchqueue" build > targets. However, i see a few issues ... > > 1) How to prevent a normal user from running it and > so bombarding the cocoon-dev list with patchqueue > summaries. As a temporary mease there should be > some warning about it. > > 2) It generates a document in src/documentation/xdocs/patches.xml > However, that changes up the developer's working copy > which is then out-of-sync with the repository. > > 3) This one may be an issue with your own computer Ken. > some (5) summaries came to the list yesterday, probably > Ken doing testing. Anyway the date of the email was null. > So they did not show up properly in the email lists. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
