From 66919bf6ec7d5da28c66af677d6df118a277e6ab Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Feb 2024 13:04:56 -0400 Subject: [PATCH] comment --- ...ment_2_6b682415956756b969767f7de267f1f0._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_2_6b682415956756b969767f7de267f1f0._comment diff --git a/doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_2_6b682415956756b969767f7de267f1f0._comment b/doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_2_6b682415956756b969767f7de267f1f0._comment new file mode 100644 index 0000000000..081ca287dc --- /dev/null +++ b/doc/tips/redacting_history_by_converting_git_files_to_annexed/comment_2_6b682415956756b969767f7de267f1f0._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2024-02-12T17:01:13Z" + content=""" +> 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 + +Right, any repository you fetch unredacted-master into, you will also want to +fetch refs/redacted/ to as well, and run git replace there, as shown in the last +code block of the tip above. +"""]]