> Ian Wells wrote:
> >
> > I keep finding comments about the need to implement a new
> system of triggers
> > which is more comprehensive and orthogonal than the current
> > commitinfo/loginfo/taginfo one. Has there been any
> progress on this (code,
> > designs, or even first thoughts) or is it still waiting for
> someone to spend
> > time on it?
>
> I'm taking a slightly different approach. I'm bashing out a perl
> adapter of sorts that you would install as the script for each *info
> file, and then it would normalize the information and allow
> you to write
> common triggers that snap into *it*. Once I have it even roughly
> working I'll release it under the Perl Artistic License.
That's fine, but I was also looking for triggers which happen on file
fetches (checkout/update/diff etc.) as well. These aren't implemented at
the moment afaics, although I found in-passing mention of a 'readers' file
that's supposed to limit access for these operations... Anyone know about
that, btw? I couldn't find any documentation on it.
