File: comment_1_120681851a595909e19afcc0334383ec._comment

package info (click to toggle)
git-annex 10.20250416-2
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,572 kB
  • sloc: haskell: 90,656; javascript: 9,103; sh: 1,469; makefile: 211; perl: 137; ansic: 44
file content (22 lines) | stat: -rw-r--r-- 862 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
[[!comment format=mdwn
 username="joey"
 subject="""comment 1"""
 date="2017-02-17T16:33:02Z"
 content="""
This message from git fsck does not indicate any kind of serious problem
with the repository.

A dangling blob can be added to a git repository when something gets
staged but is then never included in a commit. For example, with the
assistant, if a file is created, and then modified soon after, the
original version would get staged, but before it was committed, the
new version staged and included in the commit. 

There are several other scenarios, involving the assistant and not, where
that could happen.

So, git is telling you that the git repository contains
information that's not being used. Unless you are low on disk
space this probably doesn't matter, and git will automatically
clean up dangling blobs after a while (or see `git gc`).
"""]]