"Christian Rasmussen" <chr.aaroe_at_gmail.com> writes:
> Ok, so what I get from that is that it's not a direct in feature in a
> clean svn installation but something which can be achieved with neon?
>
> And to comment on epg who said I meant that the information was
> visible when committing, I must emphasize that I really did mean to
> update. I just tried it out on the repository I wrote earlier and it
> really is when updating.
>
> What I'm really curious about is how to achieve this with my server,
> because this could really be quite informative at times and I can't
> seem to find anything with google - not that I expect a guide, but
> just to know if I'm correct with me understanding that it's by this
> neon-thingy?
I don't know how TSVN implemented it; you may have to ask there, or
trace the code.
I'd first do a skeletal update between the revs, just to count the
number and types of changes. Then I'd do the real update, including
contents, using the information from the previous update to give a
progress report. This would increase latency, though. TSVN may be
doing something cleverer.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-04 03:29:42 CEST