Suggest that git annex diffdriver fetches content to diff
authornobodyinperson <nobodyinperson@web>
Sat, 29 Jul 2023 17:07:22 +0000 (17:07 +0000)
committeradmin <admin@branchable.com>
Sat, 29 Jul 2023 17:07:22 +0000 (17:07 +0000)
doc/todo/Should_git_annex_diffdriver_fetch_non-present_file.mdwn [new file with mode: 0644]

diff --git a/doc/todo/Should_git_annex_diffdriver_fetch_non-present_file.mdwn b/doc/todo/Should_git_annex_diffdriver_fetch_non-present_file.mdwn
new file mode 100644 (file)
index 0000000..e1470d8
--- /dev/null
@@ -0,0 +1,7 @@
+I noticed that `git annex diffdriver` doesn't make sure that files it tries to diff are actually present. Would it make sense that `git annex diffdriver ...` runs `git annex get` to ensure files are present? ðŸ¤” A `git diff` could then result in a lot of traffic if the user configured the `diffdriver`. But I'd say that users who took their time to configure would be are aware of this or even expect that to happen - after all they want to see the differences to a past version.
+
+A manual workaround is to handle the `get`ting in a custom supplied diffing program.
+
+Context:
+
+- [recently added `git annex diffdriver --text`](https://git-annex.branchable.com/todo/Improving_diffdriver_--text/)