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

[merge-tracking]Why we need PATH_TXN_MERGEINFO in merge-tracking?

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: 2006-09-13 12:33:52 CEST

Hi All,
This post is a result of my earlier discussion regarding the same from a
different perspective.

PATH_TXN_MERGEINFO file having hash of
'paths having svn:mergeinfo' Vs 'actual mergeinfo' has come to life at

Corresponding snip from the log reads thus,
Mergeinfo is now stored in a transaction-local file during the transaction,
and SQL is generated at commit time.

If above snip is the purpose of this implementation, I have the following
a)Why to have it has a disk-based storage?
 I am against it for the following reasons
  * As this(svn:mergeinfo) data is not meant for sharing with other
tools like 'svnadmin' and
    'svnlook', this filebased storage is a wrong choice.
     - I have a in-memory equivalent patch for the same.
  * It is a joke to keep creating new hash in memory and dump to file
within the
    same program execution context for each path having 'svn:mergeinfo'.
     - I have another patch which does the same indexing from
       'write_final_rev' without caching at all.
  * It is a data redundancy issue.

With regards
Kamesh Jayachandran

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 13 12:33:56 2006

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

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