diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2015-01-22 01:05:56 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-01-22 01:05:56 +0000 |
| commit | 009fadff9a2d1ffa010b358624203b4cb89b3073 (patch) | |
| tree | 3715bc6bcc3c0ebac2433c5a1a319620585336db /doc/design/v6 | |
| parent | 3504d2a18519df7b0e52ff525b6ea41ac43da7b9 (diff) | |
Added a comment
Diffstat (limited to 'doc/design/v6')
| -rw-r--r-- | doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment b/doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment new file mode 100644 index 000000000..9077eada9 --- /dev/null +++ b/doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" + nickname="Richard" + subject="comment 1" + date="2015-01-22T01:05:56Z" + content=""" +My gut feeling for incompatible changes in v6 is to somehow make v5 and below error out on all merges with a v6 repo. + +Conversely, v6 git-annex running in v6 repos would transition all data while merging in v5 repos. + +As a migration path for existing repos, you could move `git-annex` and `master` to `git-annex_v5` and `master_v5`. Once you are certain all known repos within that repo group are transitioned, either kill the v5 branches automagically or print info on cli/web UI on what needs to be run to get rid of them. + +Having several plain git 1+ GiB repos (i.e. without any annex objects), I would love to transition after v6 and the migration paths have been hung a month or three to dry. +"""]] |