Edgewall Software

Changes between Initial Version and Version 1 of Ticket #9980


Ignore:
Timestamp:
Jan 15, 2011, 2:05:44 PM (13 years ago)
Author:
Christian Boos
Comment:

That's by design, we only reset the metadata of the revision.

repository sync <repos> [rev]

    Resume synchronization of repositories

    It works like `resync`, except that it doesn't clear the already
    synchronized changesets, so it's a better way to resume an interrupted
    `resync`.

    See `resync` help for detailed usage.

(as you can see, the inline doc is incomplete…)

This was implemented in order to support the post-revprop hook in Subversion (#6016).

The only reason I could see to resync completely a single svn change would be in case the actual file changes changed… did they implement svnadmin backout? ;-)

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9980 – Description

    initial v1  
    1 [[[ repository resync repo revision ]]] doesn't do anything with the node_change table.  This results in an incomplete resync.  The only code I see that will resync the node_change table is a full repo resync.  Is this by design or a bug?  How does one completely resync a single svn revision? 
     1{{{ repository resync repo revision }}} doesn't do anything with the node_change table.  This results in an incomplete resync.  The only code I see that will resync the node_change table is a full repo resync.  Is this by design or a bug?  How does one completely resync a single svn revision?