Bug#704957: already fixed

Henrik Ahlgren wrote: > On Mon, Apr 08, 2013 at 12:53:52PM -0400, Joey Hess wrote: > > mv .git/annex/bad . > > git annex add bad > > rm -rf bad > > Can you please explain how that should work? When I run that, it looks > like git-annex just thinks I want to add new files, and git status > reports

Bug#704957: already fixed

On Mon, Apr 08, 2013 at 12:53:52PM -0400, Joey Hess wrote: > mv .git/annex/bad . > git annex add bad > rm -rf bad Can you please explain how that should work? When I run that, it looks like git-annex just thinks I want to add new files, and git status reports this: # On branch master # Changes t

Bug#704957: already fixed

Henrik Ahlgren wrote: > (is there a command to move the .git/annex/bad files back > into the original place automatically?) mv .git/annex/bad . git annex add bad rm -rf bad > Anyway, am I correct in assuming that the workaround would be > to use "git annex migrate" to move the troubled files to

Bug#704957: already fixed

Apologies--I did not read the changelog of more recent git-annex versions before reporting this bug, and I did not find any previous bug reports concerning this in BTS. I just noticed that this issue has already been fixed in version 3.20120825. Also, I forgot to mention that the repositories in q