Processing of syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes

syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes uploaded successfully to localhost along with the files: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1.dsc syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1.debian.tar.xz extlinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd

syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW

binary:extlinux is NEW. binary:isolinux is NEW. binary:pxelinux is NEW. binary:syslinux is NEW. binary:syslinux-common is NEW. binary:syslinux-efi is NEW. binary:syslinux-utils is NEW. binary:syslinux is NEW. binary:pxelinux is NEW. binary:extlinux is NEW. binary:syslinux-efi is NEW. binary:syslinu

Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)

Hi Holger, thanks for uploading syslinux to backports. Was there a specific reason for that I should be aware of? I believe I fixed all the important bugs in a stable point release [1]. In any case, if you think there is value in maintaining syslinux in stretch backports, I'm happy to maintain