From 0ba27bac7ef0e13788e6eb71e3089096e1a90ad4 Mon Sep 17 00:00:00 2001 From: David Bremner Date: Sun, 28 Oct 2012 20:32:25 -0300 Subject: [PATCH] fix example commands in comment --- .../comment_1_684b7b652d3a8ec04f32129c5528f1ab._comment | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/doc/walkthrough/unused_data/comment_1_684b7b652d3a8ec04f32129c5528f1ab._comment b/doc/walkthrough/unused_data/comment_1_684b7b652d3a8ec04f32129c5528f1ab._comment index cb23247030..2be2a6463f 100644 --- a/doc/walkthrough/unused_data/comment_1_684b7b652d3a8ec04f32129c5528f1ab._comment +++ b/doc/walkthrough/unused_data/comment_1_684b7b652d3a8ec04f32129c5528f1ab._comment @@ -6,8 +6,8 @@ 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 + % git annex find --format '${key}\n' | sort > /tmp/known-keys + % find .git/annex/objects -type f -exec basename {} \; | sort > /tmp/local-keys % comm -23 /tmp/local-keys /tmp/known-keys to look for what branch these are on, try @@ -17,8 +17,6 @@ to look for what branch these are on, try for one of the keys output above. In my case it was the same remote branch keeping them all alive. - - - +*EDIT* sort key lists to make comm work properly """]]