From the git repository where the tarball is generated. There is no tag there, but with commits, I can determine the commit that is corresponding to 0.5.11 release. Then I was bringing the other 4 patches on the top. If I generated the tarball from the master top revision, it would be 0.5.12 and I did not want to do that.
Later I modified the 0004-add-aarch64-and-ppc64le-support-to-audit.h.patch adding a hunk found in fedora package.
But where did 0004-add-aarch64-and-ppc64le-support-to-audit.h.patch come from? It is not exactly equal to commit fe46504.
From the git repository where the tarball is generated. There is no tag there, but with commits, I can determine the commit that is corresponding to 0.5.11 release. Then I was bringing the other 4 patches on the top. If I generated the tarball from the master top revision, it would be 0.5.12 and I did not want to do that. Later I modified the 0004-add-aarch64-and-ppc64le-support-to-audit.h.patch adding a hunk found in fedora package.