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 2016-10-26 13:57:20 -04:00
parent e818494f57
commit bd6e026e1c
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
2 changed files with 14 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/git-annex-unannex.mdwn
View file

@ -14,9 +14,10 @@ file back how it was before the add.
Note that for safety, the content of the file remains in the annex,
until you use `git annex unused` and `git annex dropunused`.
This is not the command you should use if you intentionally annexed a
file and don't want its contents any more. In that case you should use
`git annex drop` instead, and you can also `git rm` the file.
This is not the command you should use if you intentionally added a
file some time ago, and don't want its contents any more. In that
case you should use `git annex drop` instead, and you can also
`git rm` the file.
# OPTIONS

10
doc/git-annex-unannex/comment_2_d325e4201ec2964c5633e00c473df755._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2016-10-26T17:53:23Z"
content="""
The behavior your comment describes is only the case with v5
repoitories in indirect mode. With v5 direct mode repositories and
with the newer v6 repository format, `git annex unannex`
is able to safely handle files that have been added and not committed yet.
"""]]