Oops, that was the problem then. It was "application/octet-stream" because I was constructing the email with the Ruby "mail" gem that doesn't recognize ".patch" files as being text. I'll use better methods in the future.
--David On Sun, Mar 19, 2017 at 10:13 PM, NightStrike <nightstr...@gmail.com> wrote: > Do you know what content type you attached as? We have to explicitly > allow each type. The current list is: > > application/pgp-signature > multipart/mixed > multipart/alternative > multipart/signed > text/plain > text/x-patch > > If the content type is left unspecified, then the attachment is > deleted. I can add anything you like. > > On Sun, Mar 19, 2017 at 10:30 PM, David Grayson <davidegray...@gmail.com> > wrote: > > NightStrike, > > > > The mailing list swallowed the patch in the message I sent on March 16th. > > I can see in GMail that I did have a patch attached to my message, but no > > attachment is visible in the archive here: > > > > https://sourceforge.net/p/mingw-w64/mailman/message/35729302/ > > > > --David Grayson > > > > On Sun, Mar 19, 2017 at 7:03 PM, NightStrike <nightstr...@gmail.com> > wrote: > > > >> On Mar 16, 2017 1:40 PM, "Liu Hao" <lh_mo...@126.com> wrote: > >> > >> On 2017/3/17 0:51, David Grayson wrote: > >> > I was trying to compile Qt and I ran into an error because Qt is > >> > passing a const pointer to the first argument of VerQueryValue, which > >> > is not properly marked as const in the mingw-w64 header files. This > >> > patch fixes that. > >> Please send the patch both inline and as an attachment, since SF mailing > >> lists swallow attachments frequently. > >> > >> > >> It shouldn't. If it does, tell me and I'll address it. I believe I > already > >> fixed one issue you brought up a while ago. I haven't seen any since. > >> ------------------------------------------------------------ > >> ------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> Mingw-w64-public mailing list > >> Mingw-w64-public@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > >> > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Mingw-w64-public mailing list > > Mingw-w64-public@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public