From nobody Thu Jan 01 09:26:47 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dhhKr1Zw8z6Ltcr for ; Thu, 01 Jan 2026 09:26:56 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4dhhKq1k8Vz3ZHH for ; Thu, 01 Jan 2026 09:26:54 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from delta.joker.local (124-18-6-240.area1c.commufa.jp [124.18.6.240]) (authenticated bits=0) by www121.sakura.ne.jp (8.18.1/8.17.1/[SAKURA-WEB]/20201212) with ESMTPA id 6019QmM0063060; Thu, 1 Jan 2026 18:26:49 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dec.sakura.ne.jp; s=s2405; t=1767259609; bh=up8aZD5E7nCSuPVThgR7mR+vU38PSfoLxD0YeK2w+Ws=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=anPR/NF1b6NAXW5eJ9jGchgO8NM6fzejaBgdzC1Vr1728FIz8KxE7LP95WED8frPd 5Q07NVQNGOCaAB/3OB+s5fzdy4vff2KsLzO61ynUxyah7n783RGo2F4UTwivFmY1fh CY8X+RaCWDBhlfeeW9KTLrMgGtYa0bggkHwwURZM= Date: Thu, 1 Jan 2026 18:26:47 +0900 From: Tomoaki AOKI To: Paul Floyd Cc: freebsd-current@freebsd.org, marklmi@yahoo.com Subject: Re: A question on how much of my list messaging is considered inappropriate content for the lists I post to? Message-Id: <20260101182647.83e09e83e81605690b1ff0fc@dec.sakura.ne.jp> In-Reply-To: <7d2a8e91-c78b-4207-a4ab-41056333bdd5@gmail.com> References: <7d2a8e91-c78b-4207-a4ab-41056333bdd5@gmail.com> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd15.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dhhKq1k8Vz3ZHH On Thu, 1 Jan 2026 09:45:40 +0100 Paul Floyd wrote: > > On 2026-01-01 07:19, Mark Millard wrote: > > I've received a public request via part of a bugzilla > > comment on a submittal: > > > > "can you please stop treating our bug tracker and mailing > > lists as your personal blog?" > > > My suggestion is that you try to cut down unnecessary detail. It can > sometime be difficult to find what the point of your messages are. If > people ask for clarification you can always add the details later. > > A+ > > Paul Putting serialized Bugzilla comments aside. Another thing I can mention is "broken threads". Replying as top post makes traking things harder. I assume it could be because Mark is receiving ML posts as summary. Or copy&pasting from web ML archives like I do for dev-commits-* MLs. For me, basically sbscribing with regular per-post receives, but dev-commits-* ML has too many posts to handle locally. (IIRC, previous ML server linked threads even for such kind of posts.) But if anyone replies to my post CC'ing me, my reply to it can be "properly threaded afterwards". And basically my posts to dev-commits-* ML are for anything needs urgent fixes or reverts, otherwise, filing PR. (If I have patches, sometimes opening review on Phablicator, too.) Regards. -- Tomoaki AOKI