From 6ec92482b0de2e21b69997a533027b3389ab6e7b Mon Sep 17 00:00:00 2001 From: anarcat Date: Tue, 25 Aug 2015 20:03:00 +0000 Subject: [PATCH] some weird corner case, i guess --- .../removing_remote.log_information_completely.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/removing_remote.log_information_completely.mdwn diff --git a/doc/forum/removing_remote.log_information_completely.mdwn b/doc/forum/removing_remote.log_information_completely.mdwn new file mode 100644 index 0000000000..0a0e91cd40 --- /dev/null +++ b/doc/forum/removing_remote.log_information_completely.mdwn @@ -0,0 +1,9 @@ +in [[forum/remote-specific_meta-data/]], we have learned how to insert our own remote-specific metadata, in remote.log. now, we need a way to remove that data. for some reason, injecting commits in the `git-annex` branch doesn't quite work, because other assistants will overwrite that merge thanks to the [[git-union-merge]] driver. + +so far, i have found that it *can* be possible to work around this problem by repeatedly doing commits on the git-annex branch and running `git-annex sync` by hand after. it stumbles and flips around for a while, but eventually does it. it does create nice sparkles in gitk: + +![a tangled mess in gitk](http://i.imgur.com/PD4ne50.png)] + +What is the proper way of removing entries from `remote.log`? How about propagating changes to the `synced/git-annex` branch? I can generate commits on `git-annex` using the git-annex index, and on the `git-annex` branch. But how should those changes be propagated to other branches? + +Thanks! --[[anarcat]]