From 2832714af15f098102e7042731ac761de235ed09 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Sun, 11 Feb 2024 18:54:45 +0000 Subject: [PATCH] Added a comment --- ...omment_1_aece062800c6ed78988161d40e36bba4._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_1_aece062800c6ed78988161d40e36bba4._comment diff --git a/doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_1_aece062800c6ed78988161d40e36bba4._comment b/doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_1_aece062800c6ed78988161d40e36bba4._comment new file mode 100644 index 0000000000..e8af23f4c9 --- /dev/null +++ b/doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_1_aece062800c6ed78988161d40e36bba4._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 1" + date="2024-02-11T18:54:45Z" + content=""" +Thank you! In my case, since safe commit is too far in the past, what I had in mind is a little different: I wanted to have a completely disconnected history with a commit which had `$privatefile`s moved to annex, but I think the approach is \"the same\" in effect. +The only thing I would do differently is to first convert files to git-annex in `master` (to become `unredacted-master`), so I end up with the same tree in `unredacted-master` and `master` happen that later I would need to cherry-pick some changes accidentally committed (e.g. by collaborators) on top of `unredacted-master`. + +Another note worthwhile making IMHO is that AFAIK those `git replace` markers are local only, and whoever has unredacted-master later on might need to set them up as well for their local clones to make such a \"collapse\" of histories. +"""]]