summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw <Carl@web>2015-09-10 16:04:32 +0000
committerGravatar admin <admin@branchable.com>2015-09-10 16:04:32 +0000
commit28f42d886ed6257f2ecefbe2e271476625b5da68 (patch)
tree4f53001fe23ca53267e179eb6be0f8dc39cce7f7
parentbc814fc95984f835841717c28291c9e7e454fd93 (diff)
Added a comment
-rw-r--r--doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_2_fc1d755b34f29e065e536be2acfe1ee1._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_2_fc1d755b34f29e065e536be2acfe1ee1._comment b/doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_2_fc1d755b34f29e065e536be2acfe1ee1._comment
new file mode 100644
index 000000000..a230ddf5d
--- /dev/null
+++ b/doc/bugs/fsck_--incremental-schedule_does_not_work_as_documented/comment_2_fc1d755b34f29e065e536be2acfe1ee1._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw"
+ nickname="Carl"
+ subject="comment 2"
+ date="2015-09-10T16:04:32Z"
+ content="""
+I think you are right. I did try it out on the mac and Thought that I could see the same problems there. Today I tried to reproduce it, but it seems to be working correctly. (I have only tested it properly on a special remote, with --from, and not on the repo itself, since I by misstake did start a job that fsck-ed all files with a new due date in 30 days.
+
+Please close the bug.
+"""]]