> By using the {Vsv} in the loginfo script this can be worked around. I've
> attached a version of the script I was working on that shows how to get
> the necessary information out. I believe it is at least as robust as the
> CVS patched version (I believe only a file consistsing of dots, numbers,
> and commas will break this method).
How about {Vvs} and [\d\.]+,[\d\.]+,.* ??