diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-11-20 14:15:29 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-11-20 14:15:29 -0400 |
| commit | 40828a6299fde76fa78951de818b0f3c6f62b765 (patch) | |
| tree | 42a83a095aa2f42fd01c60efef1cce54f48e5a8f | |
| parent | d675f1c82e7a3c7aa3f0b3f67284433cce111781 (diff) | |
| parent | 1de00df63602bc67a19a72ec2a07821edea6619d (diff) | |
Merge branch 'master' of ssh://git-annex.branchable.com
| -rw-r--r-- | doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn b/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn index 9d1bbc4e0..46febe72e 100644 --- a/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn +++ b/doc/bugs/old_data_isn__39__t_unused_after_migration.mdwn @@ -53,3 +53,9 @@ The two files are hardlinked, so it's not taking up extra space, but it would be > still finds a file referring to the old key. > > So, slightly surprising, but not a bug. --[[Joey]] [[done]] + +>> Thanks for the explanation. In my real repository, it was a bit trickier: +>> the migration was commited to `master`, but other *remote* branches still +>> referenced those keys. I was just doing a `git pull` from a central repo, but +>> needed a `git remote update` to remove those references from `remotes/foo/master` too. +>> --Jim |