File: comment_13_1c8cc992f04fc63179094c494bd25025._comment

package info (click to toggle)
git-annex 5.20141125
  • links: PTS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 37,828 kB
  • ctags: 583
  • sloc: haskell: 42,582; sh: 1,080; ansic: 498; makefile: 316; perl: 125
file content (10 lines) | stat: -rw-r--r-- 589 bytes parent folder | download | duplicates (11) 
1
2
3
4
5
6
7
8
9
10
 
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="108.236.230.124"
 subject="I know what it is now"
 date="2014-09-19T02:43:22Z"
 content="""
These objects are the ones written by git-remote-gcrypt when pushing to a remote. That's why the weird dates, root pseudo-commit, crazy filenames, and big gpg encrypted blobs. All countermeasures that git-remote-gcrypt uses to keep your encrypted git remote safe and not leak information about what's in it.

So, this is a bug in git-remote-gcrypt. It needs to clean these objects up after pushing them! (Also after failed pushes.)
"""]]