From 363a638b805e063a16499ee92f600a162ffaf6fc Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 26 Mar 2014 17:19:58 +0000 Subject: [PATCH 1/2] Added a comment --- ...mment_1_930b40e0f68da95d335eea5bd4216126._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment diff --git a/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment b/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment new file mode 100644 index 0000000000..05aa545ef6 --- /dev/null +++ b/doc/bugs/__96__git_annex_forget_--drop-dead_--force__96_____95__revives__95___repositories/comment_1_930b40e0f68da95d335eea5bd4216126._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.41" + subject="comment 1" + date="2014-03-26T17:19:58Z" + content=""" +You still have git remotes configured with the uuid of the remote, so `git annex info` pulls that data in. Since --drop-dead removes all mention of the remote from the git-annex branch, including that its trust level is dead, the remaining info from the .git/config takes effect. + +--drop-dead could `git remote rm` but that won't help other clones of the repo that also have the dead remote. Instead, I think it may make sense for --drop-dead to avoid removing the uuid from trust.log, so it will still know this remote is dead. + +(Of course, you can easily deal with this locally by `git remote rm` yourself.) +"""]] From c1197e607c04f8831eead010cfc9d6a533a1c7dd Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 26 Mar 2014 17:26:37 +0000 Subject: [PATCH 2/2] Added a comment --- .../comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment diff --git a/doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment b/doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment new file mode 100644 index 0000000000..7ca8e19167 --- /dev/null +++ b/doc/todo/clear_file_names_in_special_remotes/comment_1_630f17c9a7ce9a77d5d5867a6e0c799b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.41" + subject="comment 1" + date="2014-03-26T17:26:37Z" + content=""" +I don't see how this can possibly be done. A single git-annex object can have any number of file names, which can change at any time. +"""]]