mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

confirmed

Browse source 
(but I need them to tell me what errors of what special remotes need a
message-id)
This commit is contained in:
Joey Hess 2023-06-23 16:17:56 -04:00
parent 6774f0bf40
commit f1714915b2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
doc/todo/machine_readable_information_about_reason_of_failure_in_enableremote.mdwn
View file

@ -5,3 +5,4 @@ May be even more generally -- if there was a robust way to obtain errors for oth
[[!meta author=yoh]] [[!meta author=yoh]]
[[!tag projects/datalad]] [[!tag projects/datalad]]
[[!tag moreinfo]] [[!tag moreinfo]]
[[!tag confirmed]]

12
doc/todo/machine_readable_information_about_reason_of_failure_in_enableremote/comment_3_1c1aaecf15ee220ed5c39def48ccd734._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2023-06-23T20:13:10Z"
content="""
enableremote supports --json-error-messages now. The error messages are not
really machine parseable. But, json error messages can also now be tagged
with a unique message-id.
So, this is entirely implementable, it just needs to determine which
specific failures of which special remotes, and add a message-id to them.
"""]]