Oleksandr Hubanov

there is no need of write access to repo to resolve a merge conflict, you shall rebase your changes on top of target branch.

Hello @NickETH , is the file you have tried to unterse coming from https://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/client/updatemgr/ ?

AMATERSE fails to unterse and if you look at file in hex, it is full of ascii and windows, seems to be an archive, but not PACK or SPACK for...

Hi @jmertic , I’m currently working in RocketSoftware and we do use this tool sometimes. Certainly can take maintainership. I have had issues with binary mode, but text mode works...

Yeap, sure, where I can details how to join the meeting?

We are working on release branch right now, once all issues resolved - there will be a release, including a zip with jar

hi, yes it can be done and does make sense as the output files sometimes are huge. Feel free to suggest a change :) i see it can be done...

 not sure if you have such a button. I believe it will be enough if name of branch starts with a issue number, like : 15-can-you-please-add-support-to-decompress-to-zipoutputstream In same time,...

sorry for a delay, added comments to PR, as well changed the target branch to be release branch.

as far as i see, we only have RECFM, LRECL and the host type. I can suggest it might be in the flags section of header, but the format is...