diff options
author | 2013-07-30 20:07:09 +0000 | |
---|---|---|
committer | 2013-07-30 20:07:09 +0000 | |
commit | 45b50c63af295630e01f93cee99a0a63ef07f287 (patch) | |
tree | 1e3c59793eb697c03c2ff9cd32ba21688dbc4cb9 | |
parent | 3b148529511f9dae6019b99aeca138773e3169fd (diff) |
Added a comment
-rw-r--r-- | doc/bugs/regression_in_direct_mode_on_windows_:_weird___96__git_annex_sync__96___behavior/comment_3_a25140eb90f6b24c1a3ca39c901694e2._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/regression_in_direct_mode_on_windows_:_weird___96__git_annex_sync__96___behavior/comment_3_a25140eb90f6b24c1a3ca39c901694e2._comment b/doc/bugs/regression_in_direct_mode_on_windows_:_weird___96__git_annex_sync__96___behavior/comment_3_a25140eb90f6b24c1a3ca39c901694e2._comment new file mode 100644 index 000000000..b608efdbe --- /dev/null +++ b/doc/bugs/regression_in_direct_mode_on_windows_:_weird___96__git_annex_sync__96___behavior/comment_3_a25140eb90f6b24c1a3ca39c901694e2._comment @@ -0,0 +1,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. +"""]] |