From 05cee8ada44126596f1cf56247fe5b9efd547b70 Mon Sep 17 00:00:00 2001 From: andrew Date: Fri, 15 Jun 2018 15:59:04 +0000 Subject: [PATCH 1/5] Added a comment --- ...8_a2bafe08ff3e7a236ba560dafc9c4d85._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment diff --git a/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment b/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment new file mode 100644 index 0000000000..87faebd6c2 --- /dev/null +++ b/doc/forum/Dealing_with_crippled_Android_file_system/comment_8_a2bafe08ff3e7a236ba560dafc9c4d85._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="andrew" + avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435" + subject="comment 8" + date="2018-06-15T15:59:04Z" + content=""" +Oh, Awesome, thanks! Great find. I'll write out some of the things I have tried: + +Create a text file called `hi.txt` from Termux in `/data/data/com.termux/files/home` AKA `$HOME`. Launch `Turbo Editor` enable `Use the Storage Access Framework` in Preferences menu. Click `Open a file` | `Open from` `Termux`, click `hi.txt`, edit file, save. Now I can see changes in Termux. Nice. + +From Termux create a new soft link, `cd`, `ln -s hi.txt hilink.txt`, then in Turbo Editor I can see both files, I can edit and save either, and see changes correctly in Termux. + +I wasn't able to find the Termux `$HOME` folder in any File Manager I tried, nor any Gallery App. + + + + +"""]] From 785cb276f0e0259c59ca769f09525e85eb954076 Mon Sep 17 00:00:00 2001 From: "andrew@2e5aa03dfdc624af77a5957dd345d28430342a9c" Date: Fri, 15 Jun 2018 22:23:58 +0000 Subject: [PATCH 2/5] posted issue --- ...h_exporttree_should_sync_files_deleted_from_the_remote.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/todo/Exporting_with_exporttree_should_sync_files_deleted_from_the_remote.mdwn diff --git a/doc/todo/Exporting_with_exporttree_should_sync_files_deleted_from_the_remote.mdwn b/doc/todo/Exporting_with_exporttree_should_sync_files_deleted_from_the_remote.mdwn new file mode 100644 index 0000000000..98ddef9f56 --- /dev/null +++ b/doc/todo/Exporting_with_exporttree_should_sync_files_deleted_from_the_remote.mdwn @@ -0,0 +1,3 @@ +If git-tracked files are removed from the remote, they don't get synced over after a "git annex fsck" and "git annex export". + +Is there some way that they could make it to the remote? I'm imagining an rsync-like behavior to copy over files that have different time stamps or file sizes. Would such a feature be welcome in git annex? From 75c4c947d5b09f1aecb264af95c7dfe014c845ce Mon Sep 17 00:00:00 2001 From: "git-annex.branchable.com@07c0f8919010cc703ae7eea746d9b494c153291f" Date: Sat, 16 Jun 2018 09:14:38 +0000 Subject: [PATCH 3/5] --- ...breaks_on_symlinking_sig-annex_to_bin.mdwn | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn diff --git a/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn b/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn new file mode 100644 index 0000000000..52b37bb3b6 --- /dev/null +++ b/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn @@ -0,0 +1,22 @@ +### Please describe the problem. + +symlinking git-annex from a unpacked tarball to the + +### What steps will reproduce the problem? + +symlink git-annex somewhere, call that symline + +### + +known fix + +[[!format sh """ +#!/bin/sh +GIT_ANNEX_PROGRAMPATH=$(realpath "$0") +export GIT_ANNEX_PROGRAMPATH +exec "$GIT_ANNEX_DIR/exe/git-annex" --library-path "$GIT_ANNEX_LD_LIBRARY_PATH" "$GIT_ANNEX_DIR/shimmed/git-annex/git-annex" "$@" + + +"""]] + +the realpath call is new From fc468eed88e3deeff78b60fde36cca943a34ed85 Mon Sep 17 00:00:00 2001 From: "git-annex.branchable.com@07c0f8919010cc703ae7eea746d9b494c153291f" Date: Sat, 16 Jun 2018 09:48:53 +0000 Subject: [PATCH 4/5] Added a comment: this one is invalid --- ...omment_1_b201c92969d0ffdac2c6b738d4abae55._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin/comment_1_b201c92969d0ffdac2c6b738d4abae55._comment diff --git a/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin/comment_1_b201c92969d0ffdac2c6b738d4abae55._comment b/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin/comment_1_b201c92969d0ffdac2c6b738d4abae55._comment new file mode 100644 index 0000000000..640460a0bf --- /dev/null +++ b/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin/comment_1_b201c92969d0ffdac2c6b738d4abae55._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="git-annex.branchable.com@07c0f8919010cc703ae7eea746d9b494c153291f" + nickname="git-annex.branchable.com" + avatar="http://cdn.libravatar.org/avatar/c5379a3fe2188b7571858c49f9db63c6" + subject="this one is invalid" + date="2018-06-16T09:48:53Z" + content=""" +i retested a few times, and the actual tool i should have used is a link to the git-annex script in the root + +sorry for the noise +"""]] From 7a44c2c8ef0af74205e4068e0f9263d0502d80e7 Mon Sep 17 00:00:00 2001 From: "git-annex.branchable.com@07c0f8919010cc703ae7eea746d9b494c153291f" Date: Sat, 16 Jun 2018 09:49:19 +0000 Subject: [PATCH 5/5] removed --- ...breaks_on_symlinking_sig-annex_to_bin.mdwn | 22 ------------------- 1 file changed, 22 deletions(-) delete mode 100644 doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn diff --git a/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn b/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn deleted file mode 100644 index 52b37bb3b6..0000000000 --- a/doc/bugs/prebuild_tarball_breaks_on_symlinking_sig-annex_to_bin.mdwn +++ /dev/null @@ -1,22 +0,0 @@ -### Please describe the problem. - -symlinking git-annex from a unpacked tarball to the - -### What steps will reproduce the problem? - -symlink git-annex somewhere, call that symline - -### - -known fix - -[[!format sh """ -#!/bin/sh -GIT_ANNEX_PROGRAMPATH=$(realpath "$0") -export GIT_ANNEX_PROGRAMPATH -exec "$GIT_ANNEX_DIR/exe/git-annex" --library-path "$GIT_ANNEX_LD_LIBRARY_PATH" "$GIT_ANNEX_DIR/shimmed/git-annex/git-annex" "$@" - - -"""]] - -the realpath call is new