> For the record, it took 9 min., and 38 sec to run `baz status' on > my copy of gcc 4.0.1.
This is really sad when you're merging two trees that have ~500 patches to merge, and you're doing a per-patch review and merge/commit. Maybe, but gcc is quite a extreme example. It contains something like 55k of files (this includes .id's, so divide it by two), and 2.5k of directories (same here). gcc would be far more managable with arch if it was split into smaller bits (c-testsuite, c, objc, java, ada, ada-testsuites, ...). Most other `big' project the time is far more managable, `baz status' for coreutils (it is quite big actually) takes 10 seconds, same command for emacs took around 50 sec. And the time will be shorter if you have the stuff cached in memory which you will have if you do it a few times, for emacs it droped the time to 8 sec. That's the scenario that led me away from tla... What does tla have to do with this? _______________________________________________ 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/
