From 1fcca1b43b1be9882baf785fc6d233f9e3c1c2f1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 9 Sep 2015 16:02:06 -0400 Subject: [PATCH] response --- ...ent_1_033f5b8f2b306c756b3f12e0a9bc6637._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/removing_remote.log_information_completely/comment_1_033f5b8f2b306c756b3f12e0a9bc6637._comment diff --git a/doc/forum/removing_remote.log_information_completely/comment_1_033f5b8f2b306c756b3f12e0a9bc6637._comment b/doc/forum/removing_remote.log_information_completely/comment_1_033f5b8f2b306c756b3f12e0a9bc6637._comment new file mode 100644 index 0000000000..762f1ef4c8 --- /dev/null +++ b/doc/forum/removing_remote.log_information_completely/comment_1_033f5b8f2b306c756b3f12e0a9bc6637._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-09-09T19:57:26Z" + content=""" +There's no guaranteed way to remove lines from log files on the git-annex +branch. A union merge can always result in a removed line being added back later. + +The thing to do is to add a new line, that has a newer timestamp and +omits the information you want to remove with new information. + +When reading the remote.log, git-annex will look for the line for a remote +that has the newest timestamp, and use it in preference to older lines. +"""]]