diff options
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -21,7 +21,7 @@ Question: Handling renames (what do to generally as updates to old branches... s ## TODO 1. ~~Read repository information from files on startup (to reinitialise repos)~~ -2. Implement upper limit on fastimport processes that run concurrently (we'll need lots of them so this might get overwhelming!) +2. ~~Implement upper limit on fastimport processes that run concurrently (we'll need lots of them so this might get overwhelming!)~~ 3. Track repo renames better to allow for cauldron renames but mgaN-1 updates (also maintain state on disk and read on startup) 4. Handle resurrections/renames from non rev-1 revisions (i.e. a simple, atomic svn mv works fine, but an svn cp -r xxxx to resurrect and old package (or restore from obsolete) will not work... restoring from obsolete is tricky as we may need to migrate changes fully in the commit (undoing changes that were made after the revision we want to restore)) 5. Write a verification routine script (validate master+branches in their final state only - if the changes that got us there are a bit wrong, then tough) |