On Monday November 13 2006 10:46 am, Alan Conway wrote: > Is it possible to get triggers to actually fix the properties rather > than just abort the commit and tell you to fix them?
I don't think so. I don't think you can modify the transaction. In anycase, I'd still prefer the "abort and have you fix it" approach for now. Getting people to fix their SVN clients to me is important. When they commit to other projects (internal to their company, other apache projects, codehaus projects, etc....), they cannot rely on a script to fix/work around their setup problems. We need to tell them to get it fixed and force them to do so. Dan > > On Mon, 2006-11-13 at 10:25 -0500, Daniel Kulp wrote: > > On Monday November 13 2006 10:14 am, Robert Greig wrote: > > > On 13/11/06, Steve Vinoski <[EMAIL PROTECTED]> wrote: > > > > I don't object at all to adding it, but seeing as how we're part > > > > of a much larger repository, could we even make such a change > > > > without getting buy-in across all the other projects sharing this > > > > repository? > > > > > > Yes that could be a problem. What we could do is put in a test at > > > the stop to do if the path of the commit starts with "qpid" so it > > > only really applies to our project. Or read a file to check which > > > commit paths to match on, since that would make it easy to roll out > > > to other projects. > > > > Before spending much time on it, you probably should send a note to > > [EMAIL PROTECTED] asking if it's possible and how to proceed. > > > > Adding hooks into SVN, even if it bails if it's not qpid, would > > affect ALL commits as processes would need to be forked to do the > > validation and such. Infrastructure would need to be involved to > > make sure that's acceptable. > > > > That all said, I'd love it. It would be great if it could be > > updated to handle all the auto_props, but even flagging the eol-style > > is a huge help. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 F:781-902-8001 [EMAIL PROTECTED]
