summaryrefslogtreecommitdiff
path: root/doc/tips
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-10-09 15:46:49 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-10-09 15:46:49 -0400
commitcd53649923ab1c49494acd17593b8ad65b7c531c (patch)
tree73d300ff2568b69dcc60b5695f89a522a0869c24 /doc/tips
parentf3d197128322981d58677ba165f7d33158e07940 (diff)
move misplaced post to forum
Diffstat (limited to 'doc/tips')
-rw-r--r--doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn13
-rw-r--r--doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment22
-rw-r--r--doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment14
-rw-r--r--doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment24
-rw-r--r--doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment19
5 files changed, 0 insertions, 92 deletions
diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn b/doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn
deleted file mode 100644
index fd654079f..000000000
--- a/doc/tips/How_To_Permanently_Delete_a_File__63__.mdwn
+++ /dev/null
@@ -1,13 +0,0 @@
-Hi,
-
-We have several large git annex repos where all of the files are on remotes and we want to got through and clean up the repositories by deleting some subset of files.
-
-What is the fastest way to permanently delete files from a git annex repository with remotes?
-
-I guess I can to ``git annex drop --numcopies=0 <file>; git rm <file>``. Does that actually delete the file permanently?
-
-Is there a faster way?
-
-Thanks,
-
-Mike
diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment
deleted file mode 100644
index c0eb14174..000000000
--- a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_1_7f2cefb0991789be5a960eb9c0a9df3f._comment
+++ /dev/null
@@ -1,22 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis"
- nickname="Mike"
- subject="comment 1"
- date="2014-10-09T17:53:04Z"
- content="""
-I experimented with this by making an empty directory with two empty files and one file with some content. I added them all, then ran ``git annex drop --numcopies=0 <file>; git rm <file>`` on one of the empty files.
-
-Interestingly, what happened is that git annex deleted the empty file from .git/annex/objects, but left the directory structure. In this case the link pointed to:
-
-.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
-
-After the drop command what was left was the following empty directory:
-
-.git/annex/objects/pX/ZJ/SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855/
-
-Also interestingly and terrifyingly, because there were two empty files, both pointed to the same object, the ``git annex drop`` command deleted the file in the objects directory, and now the second link points to nothing. The file is done.
-
-This means that if you have a git annex repository and you have two copies of a file, and you think to yourself, \"oh, let me just delete one, I don't need two\", and you use the method above, you will permanently and irrevocably delete both files. Not good.
-
-Any better ideas on how to do this?
-"""]]
diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment
deleted file mode 100644
index 959ac282f..000000000
--- a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_2_d13b456c5b3990082c16e78a50f5db91._comment
+++ /dev/null
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis"
- nickname="Mike"
- subject="comment 2"
- date="2014-10-09T18:02:59Z"
- content="""
-Tried another approach:
-
-``git annex unannex <file>; rm <file>``
-
-This does not delete the original, and it only works if you do ``git annex get <file>`` first. It won't update the remote, unless you cd into that remote and run ``git annex sync`` there. After that there is the illusion the file is done, but its content is still in .git/annex/objects. In my test case I could vim into the file in question in the objects directory and it was still there.
-
-So ``git annex drop`` deletes both copies of duplicate files and so is too dangerous to use and ``git annex unannex`` doesn't delete the file anywhere. I am a little stuck here, what do I do?
-"""]]
diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment
deleted file mode 100644
index 404d12ae4..000000000
--- a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_3_854c17ff8cb38486c4bef618d1e94919._comment
+++ /dev/null
@@ -1,24 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawmwjQzWgiD7_I3zw-_91rMRf_6qoThupis"
- nickname="Mike"
- subject="comment 3"
- date="2014-10-09T18:16:34Z"
- content="""
-OK, I should have read more before writing.
-
-It seems like the procedure is described here:
-http://git-annex.branchable.com/walkthrough/unused_data/
-
-The process is:
-1. rm files or directories
-2. git annex sync in all remotes (that is a pain, I wish I only had to do it once)
-3. git annex unused
-4. git annex dropunused
-5. Repeat 4 and 5 on any repository where the data is stored
-
-That does work for me, it is just slightly cumbersome. If there is another way or if I am missing something, please let me know.
-
-Thanks,
-
-Mike
-"""]]
diff --git a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment b/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment
deleted file mode 100644
index 6e8ddc595..000000000
--- a/doc/tips/How_To_Permanently_Delete_a_File__63__/comment_4_9572ad02bbf6845b1ab6d7c612c12a2a._comment
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!comment format=mdwn
- username="http://joeyh.name/"
- ip="209.250.56.54"
- subject="comment 4"
- date="2014-10-09T18:23:58Z"
- content="""
-This post is misplaced, it is not a tip about how to use git-annex, but a question. I will be moving it to the forum after posting this comment.
-
-The right answer is probably to run: `git annex drop $file`, with no --numcopies, no --force, etc. Just let git-annex do its job; it will check the remotes to ensure that enough copies of the file exist to make it safe to drop the content of the file from the local repository. (
-Note that --numcopies=0 is very unsafe, you're asking git-annex to delete even the last copy of your data without checking when you do that.)
-
-If your goal is to get rid of every copy of this file from every repository that has a copy, I suggest just `git rm $file; git commit`, followed by running `git annex unused` in the various repositories to clean them up.
-
-There is a faster way, which is to run `git annex drop --from $remote` for each remote that has the file. If you want to get rid of every copy of the file, for sure, you could add a --force to that.
-
-git-annex deduplicates data, so it's completely expected that if two files have the same content, dropping one will remove the content of the other.
-
-I cannot reproduce any .git/annex/objects/foo empty directories being left behind by git-annex after doing that. Perhaps you are not using a current version of git-annex?
-"""]]