From e99813cb67525d0cb7a03c915b2026667310fbf5 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 9 Feb 2024 21:58:56 +0000 Subject: [PATCH 1/3] Added a comment --- .../comment_3_4cff971451dd7038ffe8f7f2fa3b28c9._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/move_files_under_git-annex_and_graft_history__63__/comment_3_4cff971451dd7038ffe8f7f2fa3b28c9._comment diff --git a/doc/forum/move_files_under_git-annex_and_graft_history__63__/comment_3_4cff971451dd7038ffe8f7f2fa3b28c9._comment b/doc/forum/move_files_under_git-annex_and_graft_history__63__/comment_3_4cff971451dd7038ffe8f7f2fa3b28c9._comment new file mode 100644 index 0000000000..0ab0b04460 --- /dev/null +++ b/doc/forum/move_files_under_git-annex_and_graft_history__63__/comment_3_4cff971451dd7038ffe8f7f2fa3b28c9._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 3" + date="2024-02-09T21:58:56Z" + content=""" +Thank you! Yet to try/follow the steps. FWIW -- we have not pushed anything to github yet, so we have everything only locally and thus should potentially be able to not reveal older objects. +"""]] From 873c6c48efa2b54ba606f9f631c1281beda57352 Mon Sep 17 00:00:00 2001 From: psxvoid Date: Sat, 10 Feb 2024 08:11:30 +0000 Subject: [PATCH 2/3] Added a comment: This behavior should be the default one --- ...t_1_30332d3828324455600b0b452e3b6c5a._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Preserving_Directories_in_Metadata_Views/comment_1_30332d3828324455600b0b452e3b6c5a._comment diff --git a/doc/forum/Preserving_Directories_in_Metadata_Views/comment_1_30332d3828324455600b0b452e3b6c5a._comment b/doc/forum/Preserving_Directories_in_Metadata_Views/comment_1_30332d3828324455600b0b452e3b6c5a._comment new file mode 100644 index 0000000000..f07a32715b --- /dev/null +++ b/doc/forum/Preserving_Directories_in_Metadata_Views/comment_1_30332d3828324455600b0b452e3b6c5a._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="psxvoid" + avatar="http://cdn.libravatar.org/avatar/fde068fbdeabeea31e3be7aa9c55d84b" + subject="This behavior should be the default one" + date="2024-02-10T08:11:30Z" + content=""" +This behavior needs to be the default. Though, I understand that everyone have different needs. + +At least it may be better to configure the behavior via a command argument, e.g. by default `git annex view` preserves the directory structure. + +And when `--plain` argument is provided, then it would behave as it currently does - the directory structure is not preserved. + +Personally, I do not see any use cases for the active behavior because usually I set tags to many files (thousands), and it's not practical for me to see thousand files in a single directory (view tag). As a more real-world example - I've tried to prepare files to be burned into BDXL disk, and for that purpose I tagged the files I want to burn as `bdxl-disk-1` tag. I then used `ncdu` to analyze the space taken by that tag. But then when I started \"fine tuning\" what should and should not go to that disk, I found it too difficult because `git annex view` places all tagged files into a single directory. + +Are there any workarounds? I'm using git annex version `10.20231228`. +"""]] From a8acc7a11c1d66a4b3160929a82c52e1a9b245ec Mon Sep 17 00:00:00 2001 From: psxvoid Date: Sat, 10 Feb 2024 10:53:56 +0000 Subject: [PATCH 3/3] Added a comment: Update: workaround with branches --- ..._0decf76e18bb9fbc9b55e94f647a466d._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/Preserving_Directories_in_Metadata_Views/comment_2_0decf76e18bb9fbc9b55e94f647a466d._comment diff --git a/doc/forum/Preserving_Directories_in_Metadata_Views/comment_2_0decf76e18bb9fbc9b55e94f647a466d._comment b/doc/forum/Preserving_Directories_in_Metadata_Views/comment_2_0decf76e18bb9fbc9b55e94f647a466d._comment new file mode 100644 index 0000000000..7289595c72 --- /dev/null +++ b/doc/forum/Preserving_Directories_in_Metadata_Views/comment_2_0decf76e18bb9fbc9b55e94f647a466d._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="psxvoid" + avatar="http://cdn.libravatar.org/avatar/fde068fbdeabeea31e3be7aa9c55d84b" + subject="Update: workaround with branches" + date="2024-02-10T10:53:56Z" + content=""" +Seems like there is a way to use git annex as I would like, though it may not be obvious. + +In order to organize files and then burn them on to BDXL, instead of using tags, I've just switched to a new branch. +e.g.: + +```sh +git checkout -b view/bdxl +``` + +and then moved files and folders to a new folder which I intend to burn later. I've also assigned `git annex tag bdxl-disk-1 . --force` directly in this folder, so later I can see which files are burned even on the main branch (because tags are tied to git annex content and shared across branches). + +P.S.: In any case, preserving the folder structure on the first `git annex view tag=*` may be much more powerful and intuitive. +"""]]