respond and close
This commit is contained in:
parent
c719998eed
commit
5eb101b720
2 changed files with 27 additions and 0 deletions
|
@ -45,3 +45,5 @@ Additionally the key will still remain in the `git-annex` branch, I'm not sure a
|
|||
### 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)
|
||||
|
||||
I'm using git annex to manage all my personal data, thanks for making such an amazing piece of software :)
|
||||
|
||||
> [[notabug|done]] --[[Joey]]
|
||||
|
|
|
@ -0,0 +1,25 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 4"""
|
||||
date="2020-05-07T15:56:38Z"
|
||||
content="""
|
||||
`git annex get` will only complain about files that are still in the
|
||||
current branch. If you want to use `--all` though, you will have to mark
|
||||
such files as dead. git-annex otherwise has no way to differentiate between
|
||||
the last copy of a file being lost inaverdently and intentionally removed.
|
||||
|
||||
Auto-deading files would hide problems.
|
||||
|
||||
> even marking it as dead is still tracking the deadness of the file
|
||||
|
||||
You can use git-annex forget to prune that information from the git-annex
|
||||
branch, but it's completely reasonable for a git repository to retain
|
||||
history by default.
|
||||
|
||||
> Leaving aside what the status is called, how about detecting it
|
||||
> automatically on `dropunused`
|
||||
|
||||
Unused files are only unused in the head of branches, not in all the
|
||||
history of the git repository. Again, git is all about preserving the
|
||||
history of files.
|
||||
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue