[TxMt] TM2: Caching for not-found SCM files?

[Christopher Creutzig]

Hi,

my sources live in a network file system behind some complex automount
scheme, let's say /foo/bar/workarea/user/project. Whenever I open some
directory there inside TM2, I get tons of messages like these in the
system log:

> 30.01.12 11:11:34	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .git failed
> 30.01.12 11:11:34	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .hg failed
> 30.01.12 11:11:35	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .p4config failed
> 30.01.12 11:11:35	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .svn failed
> 30.01.12 11:11:36	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .git failed
> 30.01.12 11:11:36	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .hg failed
> 30.01.12 11:11:37	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .p4config failed
> 30.01.12 11:11:37	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .svn failed
> 30.01.12 11:11:37	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .git failed
> 30.01.12 11:11:38	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .hg failed
> 30.01.12 11:11:38	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .p4config failed
> 30.01.12 11:11:39	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .svn failed
> 30.01.12 11:11:39	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .git failed
> 30.01.12 11:11:40	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .hg failed
> 30.01.12 11:11:40	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .p4config failed
> 30.01.12 11:11:40	automountd[3079]	parse_entry: getmapent for map sfs.worldwide.somewhere.workarea, key .svn failed
> 30.01.12 11:11:41	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .git failed
> 30.01.12 11:11:41	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .hg failed
> 30.01.12 11:11:42	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .p4config failed
> 30.01.12 11:11:42	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.bar, key .svn failed
> 30.01.12 11:11:43	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .git failed
> 30.01.12 11:11:43	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .hg failed
> 30.01.12 11:11:43	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .p4config failed
> 30.01.12 11:11:44	automountd[3079]	parse_entry: getmapent for map auto.sfs.sol2.foo, key .svn failed


It seems that TM2 tries finding the config files all the way to the root
directory for each file or directory it sees in the directory tree. I
know TM2 development is not yet at performance tuning, I just wanted to
point out that there is a probably low-hanging fruit here.

On a related note, we are using perforce, but tend to have config files
named .perforce. Is the file name TM is looking for configurable (yet)?



Christopher