Am Freitag, 23. März 2007 schrieb Ryan Schmidt:
> I don't know if any of the existing tools do this, but it sounds to
> me like it should be possible for a post-commit hook to record
> relevant information about the commit in a database, and for a
> revision graph maker to query that database more quickly than
> querying the repository directly.
> I don't have experience with revision graphs... what does one look
> like? Can you send me a sample?
http://www.alwins-world.de/wiki/programs/kdesvn/ScreenShots, the last image is
such an example, too.
The problem behind is: you must fetch it. With my tests with kdesvn it shows,
the most time costs the fetch. Parsing that bunch of revisions isn't a
problem. I'd somettimes tried for testing generating a graph of a item in dke
repository with at this time more then 500k entries, this is impossible. You
have wait hours getting all logs.
So, what would help: a log-call where only log entries belonging to an item
existing at a specific revision would send. TortoiseSvn and kdesvn must get
the whole log, parsing it twice (from newest to oldest and back) to detect
copies/moves and so on. When only getting a specific subset of log....
Hooks into a database isn't real usable for both clients, 'cause them have to
know about. (but for the users, of course, it is, thats why the answer to
this post and not to the answer of Kylo)
Hope, its now a little bit clear whats the problem behind, but I think its
a "nice to have" not a "must be".
Received on Fri Mar 23 09:20:08 2007
- application/pgp-signature attachment: stored