Fix issue introduced in 20886264

Fixes an issue discussed in !742 (merged)

Checklist

• [*] Code modified for feature
• [*] Test suite updated
• [*] Documentation updated

Reviewer's checklist:

• Any issues marked for closing are addressed
• There is a test suite reasonably covering new functionality or modifications
• Function naming, parameters, return values, types, etc., are consistent and according to CONTRIBUTION.md
• This feature/change has adequate documentation added
• No obvious mistakes in the code

mentioned in merge request !742 (merged)

Looks good to me. A more descriptive message would be nice (e.g., This makes _gnutls_resolve_priorities() return a string that is always allocated with the gnutls memory functions). Thank you!

approved this merge request

added 1 commit

• b03a0d78 - Fix issue introduced in 20886264

Compare with previous version

added 8 commits

• b03a0d78...96f2e192 - 7 commits from branch master
• 49fda837 - Fix issue introduced in 20886264

Compare with previous version

enabled an automatic merge when the pipeline for 49fda837 succeeds

Commit message updated, waiting for pipeline...

@nmav It doesn't merge though everything is green, looks like manual merging is required

Also, why did it require an ff-merge ? That doesn't make sense if master is updated regularly... you always have to rebase and wait again 1,5h for the CI just to see that master changed again...

The goal was to have a linear history. It worked well in the beginning when I was merging patches from the list, but as we moved to the gitlab interface, I'm not sure if it was worth the trouble though. Would you want to open an issue to revise that decision?

canceled the automatic merge

added 2 commits

• 8ee1fb73 - 1 commit from branch master
• 9b53438b - Fix issue introduced in 20886264

Compare with previous version

enabled an automatic merge when the pipeline for 9b53438b succeeds

merged

mentioned in commit c0211809