forum/Duplicate entries in location tracking logsgit-annexhttp://git-annex.branchable.com/forum/Duplicate_entries_in_location_tracking_logs/git-annexikiwiki2014-08-04T08:05:37Zcomment 1http://git-annex.branchable.com/forum/Duplicate_entries_in_location_tracking_logs/comment_1_3afb76397519b8ca8b55958a344f1871/joeyh.name2014-08-03T18:59:58Z2014-08-03T18:59:58Z
<p>This is perfectly normal. The next time that file in the git-annex branch is updated for any reason, git-annex will automatically compress the two entries down to a single one. In the meantime, it has no difficulty working out which entry is more recent. This is basically why it's called a log file. <img src="http://git-annex.branchable.com/smileys/smile4.png" alt=";)" /></p>
<p>It would be possible to make the union merge code compress as it merges, but this would slow down union merging some, and make it a more conceptually complicated operation. Also, whether the old entry is present in the file or not, git will be storing a copy of that old entry, so it doesn't actually tend to make the git repository any larger. For more on this, see <a href="https://joeyh.name/blog/entry/databranches/">https://joeyh.name/blog/entry/databranches/</a></p>
comment 2http://git-annex.branchable.com/forum/Duplicate_entries_in_location_tracking_logs/comment_2_6f327444772ee1e660a12e7442162df5/zardoz2014-08-04T08:05:37Z2014-08-04T08:05:37Z
<p>Thanks for the info, Joey! As long as the git tracks the history anyway, this should not increase space consumption that much.</p>
<p>Perhaps it would be useful to have something like «git annex gc» that can clean up these things manually in some situations, e. g. to compact everything before doing a «git annex forget».</p>