summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar ExGen <ExGen@web>2016-04-03 20:15:02 +0000
committerGravatar admin <admin@branchable.com>2016-04-03 20:15:02 +0000
commit027cdffd29116ca5a0d6ee1b5c86a634fe93bb6b (patch)
tree760596e9a334184bc80437e36747e4492e153ceb
parent15c34855f7d81a4f25c0ec32ad45b013c840b4e3 (diff)
Added a comment: Found?
-rw-r--r--doc/bugs/Windows__58___git_annex_get_failed/comment_3_22809831226478bac7f9361ad8d0c79d._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/Windows__58___git_annex_get_failed/comment_3_22809831226478bac7f9361ad8d0c79d._comment b/doc/bugs/Windows__58___git_annex_get_failed/comment_3_22809831226478bac7f9361ad8d0c79d._comment
new file mode 100644
index 000000000..7ca9875f1
--- /dev/null
+++ b/doc/bugs/Windows__58___git_annex_get_failed/comment_3_22809831226478bac7f9361ad8d0c79d._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="ExGen"
+ subject="Found?"
+ date="2016-04-03T20:15:01Z"
+ content="""
+I think I found the problem: <br/>
+After I edit the file and commit, if I **lock** the file and **commit again**, the problem won't happen. <br/>
+I thought there shouldn't be a difference between committing a locked file and an unlocked file? <br/><br/>
+There is another problem too: When you unlock the file, git thinks you changed it. Maybe you could fix this too?
+"""]]