From the subversion blog:
* SVN 1.5 repositories maintain a new index called the node-origins
index This is needed to speed up certain merge operations. The index
will be lazy-populated on upgraded repositories, but can be updated on
demand by running a new tool named
svn-populate-node-origins-index(.exe). If you have a large repository
you will likely want to populate the index. New repositories, or ones
that are dumped/loaded or svnsync'ed will not need this.
* For fsfs repositories, the node-origins index will be slightly
faster and take up less disk space if the repository is reloaded or
synced. For existing repositories, the index has to be maintained in a
separate set of files that takes up extra disk space and I/O.
* For new 1.5 fsfs repositories, there is a new sharding mechanism
for storing revisions on disk. Instead of storing all revisions in one
single directory, they are now spread across multiple directories which
will be better on certain filesystems. There is a Python script you can
run to shard an exising fsfs repository though.
I think it is just an index that makes subversion faster when it is
trying to determine the ancestor history of files in the repository. It
isn't merge info so to speek.
Bob
________________________________
From: AJ Lewis [mailto:vortechs2000_at_gmail.com]
Sent: Monday, December 08, 2008 4:12 PM
To: Bob Archer
Cc: users_at_subversion.tigris.org
Subject: Re: Not seeing branch mergeinfo properties on repository
upgrade to 1.5
On Mon, Dec 8, 2008 at 1:49 PM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
SVn merge properties only exist when you do (commit) a merge.
What is the svn-populate-node-origins-index too for? I thought that
would populate the mergeinfo properties, but I must be mistaken.
Thanks,
AJ
-----Original Message-----
From: vortechs2000_at_gmail.com [mailto:vortechs2000_at_gmail.com]
Sent: Monday, December 08, 2008 12:08 PM
To: users_at_subversion.tigris.org
Subject: Not seeing branch mergeinfo properties on repository
upgrade to
1.5
Hello all,
I'm attempting to upgrade a 1.4 repository to 1.5.3 for the
purposes of
getting the merge tracking feature deployed, but I'm running
into
problems. It appears that my repository's branches are not
getting the
mergeinfo property populated for some reason. The only merge
information I can see using the tools is related to moving
files, and
there are no svn:mergeinfo properties set anywhere as far as I
can tell.
I've done both a full dump/load of the repository as well as
trying an
svnadmin upgrade + svn-populate-node-origins-index. Is there
something
else I need to do? Are there other diagnostic tools I can run
to see
what's going on?
Thank you,
AJ Lewis
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageI
d=981198
<http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessage
Id=981198>
To unsubscribe from this discussion, e-mail:
[users-unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=981298
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-08 22:18:54 CET