diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-10-26 14:13:00 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-10-26 14:13:00 -0400 |
| commit | 1a537a7aeb514b625849aa5a6ad5a01d9b9f7b0d (patch) | |
| tree | e2c1bae12405ea5173631a391f3b607d99ea06fd | |
| parent | 8c97232005fa71697281c947d10482a8950160b3 (diff) | |
comment
| -rw-r--r-- | doc/bugs/All_inodes_eaten/comment_3_865c75eeee3479321f4c0f00d34e063d._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/All_inodes_eaten/comment_3_865c75eeee3479321f4c0f00d34e063d._comment b/doc/bugs/All_inodes_eaten/comment_3_865c75eeee3479321f4c0f00d34e063d._comment new file mode 100644 index 000000000..a28c499db --- /dev/null +++ b/doc/bugs/All_inodes_eaten/comment_3_865c75eeee3479321f4c0f00d34e063d._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-10-26T18:07:51Z" + content=""" +Well these look like the names I'd expect to see used for encrypted files. + +If you had the assistant watching some files that were frequently changing, +then it could lead to something like this, since many commits would be made +of many versions of a file, and each version backed up to a new encrypted +file in the special remote. You can take a look at `git log -S` in the git +repository and see if there are many commits of some of your files. +"""]] |