Changes between Version 1 and Version 2 of Ticket #11864, comment 3
- Timestamp:
- Dec 5, 2014, 3:09:38 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11864, comment 3
v1 v2 4 4 You are right, it works. I was expecting the lookup to occur dynamically regardless of whether the changeset is cached or not. Just changing `trac_user_rlookup` from `false` -> `true` is not enough, the repository must be resynced. 5 5 6 Since the replaced username is saved in the `Revision` table, the [TracIni#git-section option documentation] that states //costly if you have many users// seem slightly misleading because while it might slow down the sync, it shouldn't slow down any of the views, right? 6 Since the replaced username is saved in the `Revision` table, the [TracIni#git-section option documentation] that states //costly if you have many users// seem slightly misleading because while it might slow down the sync, it shouldn't slow down any of the views, right? I'm assuming //costly// implies that requests might be slower.