From Ryan,

I believe I have found a bug in how you calculate code changes in accurev. It appears as if you currently take the stream specified in the repo and determine all of it's parents until you encounter a snapshot or the top of the depot. And then you check that list of streams for any code changes. You should also check for streams that have time locks on them. Streams that are time locked are just like snapshots in that any code changes above them won't trickle down. But you should also check the time locked stream for code checkin on that stream (not sure if you do that for a snapshot; assume you don't). You can determine if a stream is timelocked from the cli by running accurev show -s <streamname> streams -fx and looking for the "time" element. If it exists, you have a time locked stream.