mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2017-02-17 12:36:23 -04:00
parent e93d4bfa85
commit f36d789eef
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
doc/forum/dangling_blobs/comment_1_120681851a595909e19afcc0334383ec._comment Normal file
View file

@ -0,0 +1,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`).
"""]]