On Tue, 2010-08-10, C. Michael Pilato wrote: > On 08/10/2010 01:25 PM, Julian Foad wrote: > > Oh? All I know about Andrew's particular requirements related to this > > query is what's quoted above - "If I ... accidentally leave the banned > > buildlog.htm file in ..." - which sounded vaguely like a requirement for > > a path-based rule. Maybe I missed something. > > I don't think you missed the requirement. You merely offered a > non-solution. :-) Andrew said (essentially), "I need path-based rule > enforcement, but the one you offer -- the pre-commit hook -- has this nasty > side effect of only kicking in after the entire commit payload is on the > server." You replied, "No - there are two different hooks, for precisely > this reason." But Andrew can't benefit from that other hook, because it > can't do path-based rule enforcement.
D'oh. I was stupid and didn't check. I wrongly thought - or guessed - the start-commit hook had the list of file paths available, just without the files' new text, but in fact it gets only # [1] REPOS-PATH (the path to this repository) # [2] USER (the authenticated user attempting to commit) # [3] CAPABILITIES (a colon-separated list of capabilities reported # by the client; see note below) Thanks. - Julian
