aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/regression_in_direct_mode_on_windows___58___weird___96__git_annex_sync__96___behavior/comment_3_a25140eb90f6b24c1a3ca39c901694e2._comment
blob: b608efdbef604f3f254a30c12881459cb78e8406 (plain)
1
2
3
4
5
6
7
8
9
10
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.154.0.21"
 subject="comment 3"
 date="2013-07-30T20:07:09Z"
 content="""
Yeah, I inverted some logic. This also affects, for example, git-annex on Android. Sigh. Sorry about this.

I suppose that, if you run into this bug, the best way to fix up after it is to `git-revert -n` the bad commit that sync made. Then run `git annex sync` with the fixed git-annex to commit the reversion.
"""]]