From 9ad9e1eb6577a2e1a3aec9bd4d041c7f1216ff06 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 27 May 2021 12:23:57 -0400 Subject: [PATCH] comment --- ...ent_5_d549796a3b1bdd3e980cb2c05f30fe2e._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/git-annex-unannex/comment_5_d549796a3b1bdd3e980cb2c05f30fe2e._comment diff --git a/doc/git-annex-unannex/comment_5_d549796a3b1bdd3e980cb2c05f30fe2e._comment b/doc/git-annex-unannex/comment_5_d549796a3b1bdd3e980cb2c05f30fe2e._comment new file mode 100644 index 0000000000..306233a424 --- /dev/null +++ b/doc/git-annex-unannex/comment_5_d549796a3b1bdd3e980cb2c05f30fe2e._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2021-05-27T16:20:11Z" + content=""" +@datamanager the `git-annex unannex` command can't rewrite git history, +it just stops further tracking of an annexed file by git. Any way you would +usually scrub an unwanted commit out of git's history can be used with +git-annex; scrubbing mentioned of hashes out of the git-annex branch's +history gets more involved. + +Once you have run `git-annex unannex` on a file, it's not annexed, so +commands like `git-annex whereis` will not have anything to say about it. +"""]]