merge: Support --json and --json-error-messages and --json-progress
Seems unlikely to be very useful, but trivial. And, this completes the story that git-annex sync does not need json, since every sub-operation is available in a command that does support json. (Well, except for committing, but that's not a git-annex command.) Sponsored-By: the NIH-funded NICEMAN (ReproNim TR&D3) project
This commit is contained in:
parent
daaf7e10be
commit
c98fb0b637
4 changed files with 17 additions and 8 deletions
|
@ -37,15 +37,13 @@ These commands have been updated to support --json:
|
|||
* git-annex-reinject
|
||||
* git-annex-renameremote
|
||||
* git-annex-importfeed
|
||||
* git-annex-merge
|
||||
|
||||
Provisional list of commands that don't support --json and maybe should:
|
||||
|
||||
(Feel free to reorder things to the top)
|
||||
|
||||
* git-annex-configremote
|
||||
* git-annex-enableremote
|
||||
* git-annex-initremote
|
||||
* git-annex-merge
|
||||
* git-annex-upgrade
|
||||
|
||||
These commands could support json, but I punted:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue