close not really a bug, and improve fsck man page
This commit is contained in:
parent
a0afbdc400
commit
1345f99d85
3 changed files with 28 additions and 4 deletions
|
@ -74,3 +74,4 @@ sc@section9 ~> cat /etc/issue
|
|||
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
|
||||
|
||||
|
||||
> [[notabug|done]] (I did add some more detail to the man page tho) --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,18 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2020-04-27T16:02:29Z"
|
||||
content="""
|
||||
fsck finds problems with the repository.
|
||||
|
||||
A file not being present in the local repository is not a problem, if the
|
||||
file is known to be present in some other repository.
|
||||
|
||||
The ability to have some files not present in the local repository, but
|
||||
retreivable by `git annex get` when you need them, is one of the main
|
||||
features of git-annex, since it lets you manage quantities of data larger
|
||||
than you have space for on your computer.
|
||||
|
||||
If you want to know what files are not present in your local repository,
|
||||
there is a way to do that: `git annex find --not --in here`
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue