> Maybe it is a good idea to also mention it in the DEP-3 headers for future reference.
Thank you for noticing this! It looks like I neglected to mention this. Actually I think maybe I accidentally got the backport correct because I used a local diff, thinking that there was only one commit that the diff came from when in fact there were two. So I was a bit alarmed and wanted to be sure that I didn't miss anything.
I've checked carefully to confirm that the backport is exactly from these two commits, except for the unused code paths that I removed, and that there are no other commits involved. `git log upstream/main -- agents/azure_arm/fence_azure_arm.py lib/azure_fence.py.py` shows nothing else.
I will add the second commit to the dep3 headers as you suggested.
> I noticed part of this patch is also a backport of this other upstream commit:
> https:/ /github. com/ClusterLabs /fence- agents/ commit/ cb1ff52c1445148 2dc1faf9aa660a8 c525097f94
> Maybe it is a good idea to also mention it in the DEP-3 headers for future reference.
Thank you for noticing this! It looks like I neglected to mention this. Actually I think maybe I accidentally got the backport correct because I used a local diff, thinking that there was only one commit that the diff came from when in fact there were two. So I was a bit alarmed and wanted to be sure that I didn't miss anything.
I've checked carefully to confirm that the backport is exactly from these two commits, except for the unused code paths that I removed, and that there are no other commits involved. `git log upstream/main -- agents/ azure_arm/ fence_azure_ arm.py lib/azure_ fence.py. py` shows nothing else.
I will add the second commit to the dep3 headers as you suggested.
Thank you for the review!