From e6b9d2a4304a2ebd6f556ab21e46fdf0d337cfc3 Mon Sep 17 00:00:00 2001 From: Jack Date: Thu, 8 Jun 2023 22:42:59 +0000 Subject: [PATCH 1/4] --- ...set_only_keep_current_version_in_repo.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/set_only_keep_current_version_in_repo.mdwn diff --git a/doc/forum/set_only_keep_current_version_in_repo.mdwn b/doc/forum/set_only_keep_current_version_in_repo.mdwn new file mode 100644 index 0000000000..7fd0fb414e --- /dev/null +++ b/doc/forum/set_only_keep_current_version_in_repo.mdwn @@ -0,0 +1,22 @@ +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 From b231083a37b43b8473f299f08ec456a09e7c6e65 Mon Sep 17 00:00:00 2001 From: Jack Date: Thu, 8 Jun 2023 22:44:37 +0000 Subject: [PATCH 2/4] --- doc/forum/set_only_keep_current_version_in_repo.mdwn | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/forum/set_only_keep_current_version_in_repo.mdwn b/doc/forum/set_only_keep_current_version_in_repo.mdwn index 7fd0fb414e..8f077ec42d 100644 --- a/doc/forum/set_only_keep_current_version_in_repo.mdwn +++ b/doc/forum/set_only_keep_current_version_in_repo.mdwn @@ -10,6 +10,7 @@ git annex group harddrive backup ``` and for the laptop with + ```shell git annex wanted laptop standard git annex group laptop incrementalbackup From dbeedc1fede2d1c24bb76d261a76893733681812 Mon Sep 17 00:00:00 2001 From: Jack Date: Thu, 8 Jun 2023 22:45:06 +0000 Subject: [PATCH 3/4] rename forum/set_only_keep_current_version_in_repo.mdwn to forum/only_keep_current_version_of_files_in_repo.mdwn --- ..._repo.mdwn => only_keep_current_version_of_files_in_repo.mdwn} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename doc/forum/{set_only_keep_current_version_in_repo.mdwn => only_keep_current_version_of_files_in_repo.mdwn} (100%) diff --git a/doc/forum/set_only_keep_current_version_in_repo.mdwn b/doc/forum/only_keep_current_version_of_files_in_repo.mdwn similarity index 100% rename from doc/forum/set_only_keep_current_version_in_repo.mdwn rename to doc/forum/only_keep_current_version_of_files_in_repo.mdwn From 97646765e2c7bf8f12c2c3b211de09a01d3fd858 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 9 Jun 2023 18:47:23 +0000 Subject: [PATCH 4/4] initial todo/question for easing --- .../a_way_to_figure_out_the_origin_of_largefiles.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/a_way_to_figure_out_the_origin_of_largefiles.mdwn diff --git a/doc/todo/a_way_to_figure_out_the_origin_of_largefiles.mdwn b/doc/todo/a_way_to_figure_out_the_origin_of_largefiles.mdwn new file mode 100644 index 0000000000..90b4d80fff --- /dev/null +++ b/doc/todo/a_way_to_figure_out_the_origin_of_largefiles.mdwn @@ -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]]