comment

diff --git a/doc/bugs/prevent_silent_data_loss_on_unlocked_files/comment_3_704ecfd2888a8153eaa5e4a8e6e3d011._comment b/doc/bugs/prevent_silent_data_loss_on_unlocked_files/comment_3_704ecfd2888a8153eaa5e4a8e6e3d011._comment
new file mode 100644 (file)
index 0000000..8cc0df8
--- /dev/null
+++ b/doc/bugs/prevent_silent_data_loss_on_unlocked_files/comment_3_704ecfd2888a8153eaa5e4a8e6e3d011._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2022-02-22T15:48:20Z"
+ content="""
+If it errored, git would ignore the failure and still add the file
+content to git.
+
+One thing that could be done is to come up with some kind of format for the
+lines after the annex link in the pointer file, to be used in whatever
+future expansion might happen. Then it could warn if there is data there
+not matching that format. And then add the file to the annex, to at least
+keep that data out of the git repository.
+"""]]