mirror of
https://github.com/facebook/sapling.git
synced 2024-10-11 01:07:15 +03:00
63690b7aa7
Summary: A bit of history first. For some time we had a problem in our cross repo sync library where it used the "current" commit sync version, where "current" meant "the latest commit sync config version that was added". That was incorrect, and we migrated away from this model, however there were still a few places that used get_current_mover_DEPRECATED() mover. Removing this method from a test file is easy, but it's trickier for sync_diamond_merge tool. This tool is used to sync a diamond merge from a small repo to a large repo (this is non-trivial to do, so we don't do it automatically). To make things simpler this diff requires all involved commits (i.e. both parents, where to rebase (onto) and root of the diamond merge) to have the same commit sync config versions. Reviewed By: markbt Differential Revision: D25612492 fbshipit-source-id: 6483eed9698551920fb1cf240218db7b7e78f7bd |
||
|---|---|---|
| .. | ||
| backsyncer | ||
| bookmark_renaming | ||
| bookmarks_validator | ||
| commit_validator | ||
| cross_repo_sync | ||
| live_commit_sync_config | ||
| megarepo | ||
| mononoke_x_repo_sync_job | ||
| movers | ||
| synced_commit_mapping | ||