> $ strace -o ,,s -e stat,stat64,open tla changes
For me the problem stops right here: `tla changes' necessarily operates on
the whole project, just like all other commands. Performance would be
drastically improved if `tla' only looked at the files it needs to perform
a given command, and if the user could specify those files.
I generally operate within a subtree of my `emacs' project. And when
I commit, I generally know which files I'm committing, so I can pass them to
`tla' just fine. Part of this is a UI issue, other part is implementation.
But the ID-tagging and the repository format seem innocent here.
Other implementation limitation: it always constructs a whole tree when it
really only needs "file FOO from revision BAR".
Stefan
_______________________________________________
Gnu-arch-users mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
