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

comment and improve man page

Browse source
This commit is contained in:
Joey Hess 2015-04-29 13:25:10 -04:00
parent ddcdf94162
commit cda2f83bad
2 changed files with 20 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

17
doc/bugs/clean-duplicates_causes_data_loss/comment_2_14c5c3417f107a3619a4402f75bc0002._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2015-04-29T17:18:17Z"
content="""
--clean-duplicates is not really intended to go do a full verification
that the annexed content is present. I can see how this is surprising;
it would probably be better if it were named "--clean-seen-content"
or something like that.
But, --deduplicate has the same behavior for such files, and I can't see a
way to rename that more effectively.
For now I have improved the git-annex-import man page to note that
annexed content that's been removed would make a file be considered a
duplicate.
"""]]

5
doc/git-annex-import.mdwn
View file

@ -16,8 +16,9 @@ If a directory is specified, the entire directory is imported.
When importing files, there's a possibility of importing a duplicate
of a file that is already known to git-annex -- its content is either
present in the local repository already, or git-annex knows of anther
repository that contains it.
present in the local repository already, or git-annex knows of another
repository that contains it, or it was present in the annex before but has
been removed now.
By default, importing a duplicate of a known file will result in
a new filename being added to the repository, so the duplicate file