diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2018-02-22 12:59:44 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2018-02-22 12:59:44 -0400 |
| commit | 044842dc64f7adaf0cfe30ea807bc4f8cd3e424d (patch) | |
| tree | be10126cb8b9453fbe80d259de9c5d3176bf9461 | |
| parent | dff77afb1d4de34ad9de95ba039471f7c4ba3345 (diff) | |
response
| -rw-r--r-- | doc/internals/comment_7_9c82a2878f3feb1b2a95662ed25b234b._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/internals/comment_7_9c82a2878f3feb1b2a95662ed25b234b._comment b/doc/internals/comment_7_9c82a2878f3feb1b2a95662ed25b234b._comment new file mode 100644 index 000000000..d8034bb5f --- /dev/null +++ b/doc/internals/comment_7_9c82a2878f3feb1b2a95662ed25b234b._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2018-02-22T16:56:13Z" + content=""" +@arseny-n the misctemp directory does not normally contain anything, or +only temp files in use by the currently running git-annex process for a +short amount of time. The only way I know of that it can get files piled up +in it is when you kill the git-annex process while it's using such a file. + +It's always safe to delete the files in misctemp as long as git-annex is +not running. Also, the names of the files should give a pretty good clue +about what git-annex was using the file for. For example "jlog" files are +used for staging the journal. +"""]] |