Opened 13 years ago
Last modified 7 years ago
#9980 closed defect
resync single revision doesn't resync the node_change table — at Version 1
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12.3 |
| Component: | version control | Version: | |
| Severity: | normal | Keywords: | documentation |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
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?
Note:
See TracTickets
for help on using tickets.
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? ;-)