> This sounds a lot likehttp://trac.edgewall.org/ticket/3470can you have > a look?
Yeah, that looks like the same thing; the files that haven't been changed in that repo are getting the age/last changed of the latest insert, and the ones that have been changed do have correct info. Somehow I had missed the pattern, but it looks right. I wonder if this would also be fixed (in my case) by a real fix to the other question I've recently posted: the secondary repo in this configuration is the one that the files were moved from, so if trac could see the changesets for all the files that haven't been changed yet, maybe it would just fix itself. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
