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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2023-06-09 16:14:25 -04:00
commit 3911e1061c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 31 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/forum/only_keep_current_version_of_files_in_repo.mdwn Normal file
View file

@ -0,0 +1,23 @@
Hi,
I have a repo on a server, my laptop, and a separate backup hard drive. In the repo I have many small files as well as several very large files that are present in several versions. I want to set up my repos such that my backup hard drive has everything on it, my server has only the most recent version of the large files (the server is shared, so I don't want to hog disk space), and my laptop doesn't keep annexed files locally.
I think I can probably achieve what I want for the hard drive with
```shell
git annex wanted harddrive standard
git annex group harddrive backup
```
and for the laptop with
```shell
git annex wanted laptop standard
git annex group laptop incrementalbackup
```
but I haven't been able to figure out how to setup the server so it keeps the current copy of large files but not their old versions. Do you have any suggestions?
Alternatively, I might be able to do it manually, but haven't been able to figure out how to specifically drop old versions of a file, so I would be open to suggestions on that front too.
Thanks!
-Jack

8
doc/todo/a_way_to_figure_out_the_origin_of_largefiles.mdwn Normal file
View file

@ -0,0 +1,8 @@
we spent some time scratching our heads while trying to figure out WTF git-annex was adding some mouse atlas `.nii` file into `git` while `.gitattributes` had it set so it wouldn't and nothing was in `git annex vicfg` to only then realize that there is also generic `git config annex.largefiles` which effects it.
I wondered if there could be some kind of a "mix" between `git check-attr [PATH]`, `git annex config`, and `git config --list --show-origin` which would not just state the final decision (not large) for a given PATH but also based on what value of `annex.largefiles` it did it and where it got it from (the `.gitattributes`? `git annex config`? `git config` file/option as via `--show-origin`?)
I guess the same functionality might be useful for some other options which could be picked from various sources.
[[!meta author=yoh]]
[[!tag projects/dandi]]