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 2020-03-09 12:07:03 -04:00
commit 6eb52cf5f1
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
13 changed files with 311 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/todo/add_option_to_disable_fsck_upgradable_key_warnings.mdwn Normal file
View file

@ -0,0 +1 @@
Currently [[`git-annex-fsck`|git-annex-fsck]] gives a warning for all my files stored with MD5 keys that they can be upgraded to the more secure SHA256: `Can be upgraded to an improved key format. You can do so by running: git annex migrate`. In my case the key choice is deliberate, so it would be good if this warning could be disabled, to prevent it from drowning out more serious ones.

11
doc/todo/better_error_messages_for_local_remote/comment_1_094e6a7b62c8b81185cda06a62104f1f._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="thk"
avatar="http://cdn.libravatar.org/avatar/bfef10a428769701aeee1db978951461"
subject="Also no clear error for permission problems"
date="2020-03-06T17:51:20Z"
content="""
I was exporting (with exporttree) to a directory remote on an external ext4 formatted USB drive.
As is usually the case, there was permission problem. My current user did not have write permission for one directory I was exporting to.
git-annex just printed \"failed\" after it actually completed the file transfer with 100%.
Even with --verbose and --debug I could not figure out the problem until I discovered the permission problem.
"""]]

8
doc/todo/better_error_messages_for_local_remote/comment_2_4c8115fa0a41bd1cbecdcf7a4d9608ed._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="thk"
avatar="http://cdn.libravatar.org/avatar/bfef10a428769701aeee1db978951461"
subject="No clear error message for failing names on NTFS"
date="2020-03-07T12:50:19Z"
content="""
I tried to export a tree to NTFS with a filename that contained spaces, single quotes and dots. Only after removing all of them the export succeeded. There error messages was just \"failed\".
"""]]