TW
As this is not specific to 1.0.x, I am moving this to 1.1.x milestone.
I'll update this list here with whatever we come up with: ``` # generic return codes used by borg 0 OK 1 WARNING 2 ERROR # 3 .. 63 reserved...
I'll update this list with other related issues we find: - #61 - #3446
No, rc 0 1 2 need to stay as is. There are enough free codes without changing these. @fantasya-pbem I've updated https://github.com/borgbackup/borg/issues/6756#issuecomment-1147245734 .
hmm, if we only reserve space for warnings/errors, we only have 0 for success / information. not sure if that is a problem / limitation in practice.
@m3nu @sophie-h ^^^
For errors (fatal stuff that leads to immediate termination) we can deal rather easily with them: raise an Exception, let the exit handler deal with the exception. For warnings (stuff...
Is there some systematic in the Code (guess it means the return code, rc) column (except that >= 64 is a warning)? Where do the numbers seen there come from?
Would be good to have this in the beta releases, which will likely come next after alpha4 (released today).
@fantasya-pbem are you still working on this?