On Thu, Mar 30, 2017 at 01:49:16PM +0200, zyx wrote: > Right. It had been just a coincidence that two people here reported one > same issue and I happen to fix it without the reference (also because I > didn't use Agostino's reference, but that other person's).
I think it would be greatly appreciated (from me at least), if the CVE IDs were to be included in the commit message. That would be more than enough to reference such issues unambiguously. > I had a private chat with Agostino on Tuesday, he asked me to drop a > commit link to his blog post when the change references one of those > issues, from which I understood that he'll update the Debian summary > page (link given earlier in this thread). I also can update that summary page whenever is needed (talking about https://security-tracker.debian.org/tracker/source-package/libpodofo, and all of those referenced from there) If you need so feel free to drop me a line. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Podofo-users mailing list Podofo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/podofo-users
