| 15 | | because both rely on invoking `darcs changes <file>`. |
| | 15 | because both rely on invoking `darcs changes <file>` (for that matter, that's not completely true for the |
| | 16 | [http://progetti.arstecnica.it/trac+darcs trac darcs plugin] as it does not execute that command |
| | 17 | on a per-file basis, but rather it loads and caches into its own database the result of `darcs changes -v` |
| | 18 | on the "not-yet-loaded" changesets, visiting every patch in the repository just once. |
| | 19 | It caches also the actual content of each file touched by any browsed changeset, to compute the unidiff.). |