diff options
| author |  http://joeyh.name/ <joey@web> | 2013-05-13 18:28:01 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-05-13 18:28:01 +0000 |
| commit | d42d9b7d5400be5f80d7d36dc9d23094d70ed028 (patch) | |
| tree | b56bdd7d684f45705d5e361813d37093830096b1 | |
| parent | eff5ccd9ca0e0c7afa2d47865d3e6e1fb679c9a7 (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/Does_migrate_ensure_data_integrity__63__/comment_1_cef50b32c46f4406c6f918c5866ddc15._comment | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/Does_migrate_ensure_data_integrity__63__/comment_1_cef50b32c46f4406c6f918c5866ddc15._comment b/doc/forum/Does_migrate_ensure_data_integrity__63__/comment_1_cef50b32c46f4406c6f918c5866ddc15._comment new file mode 100644 index 000000000..7c819a8ca --- /dev/null +++ b/doc/forum/Does_migrate_ensure_data_integrity__63__/comment_1_cef50b32c46f4406c6f918c5866ddc15._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 1" + date="2013-05-13T18:28:01Z" + content=""" +I actually didn't originally consider this, but it turns out I have wonderful users, and you're at least the second to consider this case. + +So the released git-annex version does already verify the checksum when doing a migration. However, as I was checking this, I noticed +I had left a window between the verification and the generation of the new key for the migration. It's pretty unlikely a file would get corrupted just as it was being migrated, but that's no excuse. I've committed a change that reverses the order; so it generates a new key and then verifies the old one. +"""]] |