diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck <Jim@web> | 2011-11-18 21:12:30 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-11-18 21:12:30 +0000 |
| commit | 1de00df63602bc67a19a72ec2a07821edea6619d (patch) | |
| tree | 20c5a3a82a2c30d88ad6a7eab8cb2e3de5361811 | |
| parent | c50a5fbeb4f90041f16cc84bf6b39577655d42b6 (diff) | |
| -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 |