Thanks for this, will look into testing and merging after I push my local changes to master.

Will this be merged? This is a very very useful thing that we miss now.

Not for next release. The changes in this pull (not branch) are broken.

Then should I reimplement this with the up-to-date repo?

Like I said, current branch issues against master are not the issue, but the initial pull request changes submitted are, even though it was a clean code. There is a pretty big logical one too, should be noticeable to others too, one million imaginary dollar to whoever figures it out first... ;)

There also other issues as well regarding how this should ideally be implemented. Redoing with up-to-data master won't fix them. Fixing them all would be time consuming, time which I currently don't have since other higher priority things are being worked on, likely no time for testing either, unless someone else fixes them all as per quality and security standards required.

May I hope to get this PR merged into master this year?

Possibly this year, but not for next release or next 1-2 months if I have to do it.

Possibly this year, but not for next release or next 1-2 months if I have to do it.

Its been very long since I have been waiting for this issue to be solved. No idea what other maintainers are doing. 😓

Hope this nice SAF file manipulation feature will be merged before the next release.