[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Log caching vs. merge tracking

From: <Stefan.Fuhrmann_at_etas.de>
Date: 2007-06-24 12:37:52 CEST

Hi devs,

my belief is that TSVN needs full merge tracking
information for features like the revision graph.
That is: all svn:mergeinfo property changes for
all paths in all revisions (if they changed).

Even the newest SVN log API does not provide
that information: it does not tell what revisions
have been merged / unmerged from what path
to where.

There seems to be no API to get that information
*efficiently*, i.e. without zillions of individual calls
to get_merge_info (?) taking hours for a single
"large" revision. I will ask the SVN devs about it.

However, I think we do need the full merge info.
Therefore, I added the respective data containers
and interfaces to the log caching infrastructure.

My questions:

* Do you agree that we should store / process
  the whole merge info?
* How would the merge info be represented in
  e.g. the log dialog?
* Is it o.k. to stick with the current log interface
  and not to mimic the latest "include merge-tree"
  log feature?

If questions 1 und 3 are answered "yes", I can
merge the latest changes (merge-tracking and
cache updates) to trunk.

-- Stefan^2.
Received on Sun Jun 24 12:37:36 2007

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.