From owner-freebsd-current@freebsd.org Tue Nov 17 13:19:20 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A459E2ECB9E for ; Tue, 17 Nov 2020 13:19:20 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Cb63W5qs1z4f5f for ; Tue, 17 Nov 2020 13:19:19 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.93.0.4 (FreeBSD)) (envelope-from ) id 1kf0t4-000GMq-Mj; Tue, 17 Nov 2020 13:19:10 +0000 Date: Tue, 17 Nov 2020 13:19:10 +0000 From: Gary Palmer To: Thomas Mueller Cc: freebsd-current@freebsd.org Subject: Re: in -current is svn still canonical? Message-ID: <20201117131910.GA46155@in-addr.com> References: <5fb33a11.1c69fb81.2d2a6.f92eSMTPIN_ADDED_MISSING@mx.google.com> <5fb35900.1c69fb81.7679c.a50eSMTPIN_ADDED_MISSING@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-Rspamd-Queue-Id: 4Cb63W5qs1z4f5f X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2020 13:19:20 -0000 On Tue, Nov 17, 2020 at 09:25:32AM +0000, Thomas Mueller wrote: > from Warner Losh and my last message: > > > > Thanks for the information, but if you feel the need to send me a > > > not-quite-CC, please don't send me the multipart/alternative version when > > > you send the plain-text version to the list. > > > > I hate multipart/alternative! > > > I must apologize. Sadly, I use gmail, so I have no control over how it > > decides to encode things, sadly. I've tried in the past, and alas, nothing > > I've tried works for any length of time. Please forgive me whatever > > unspeakable MIME atrocities it sends on my behalf. I've removed you from > > the cc line in the hopes that the FreeBSD mail server cleans things up to > > be more to your liking. > > The message on the list had only the plain-text part. Either you sent it differently, or the list server stripped the HTML attachment. > The mailing list software is set to strip all non-plain-text content. This is why you sometimes see mails with no body content. The sender sent a mail which only had a HTML part and it was stripped, and without an alternate MIME part there was nothing to send. Regards, Gary