Added a comment: finding data that isn't unused, but should be.
This commit is contained in:
parent
9762d26f81
commit
c2a2d226af
1 changed files with 24 additions and 0 deletions
|
@ -0,0 +1,24 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="bremner"
|
||||||
|
ip="156.34.89.108"
|
||||||
|
subject="finding data that isn't unused, but should be."
|
||||||
|
date="2012-10-17T20:32:11Z"
|
||||||
|
content="""
|
||||||
|
Sometimes links to annexed data still exists on some branch, when it was supposed to be dropped. Here is how I found these; perhaps there is a simpler way.
|
||||||
|
|
||||||
|
% git annex find --format '${key}\n' > /tmp/known-keys
|
||||||
|
% find .git/annex/objects -type f -exec basename {} \; > /tmp/local-keys
|
||||||
|
% comm -23 /tmp/local-keys /tmp/known-keys
|
||||||
|
|
||||||
|
to look for what branch these are on, try
|
||||||
|
|
||||||
|
% git log --stat --all -S$key
|
||||||
|
|
||||||
|
for one of the keys output above. In my case it was the same remote branch keeping them all alive.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
"""]]
|
Loading…
Reference in a new issue