From: Graham Perrin <grahamperrin@gmail.com> To: freebsd-current@freebsd.org Subject: Re: A question on how much of my list messaging is considered inappropriate content for the lists I post to? In-Reply-To: <358ACE63-4FC7-451B-8002-D24B283FCB6D@gmail.com> References: <BED67752-363D-46EE-8DD6-7FDDC6998EE8.ref@yahoo.com> <BED67752-363D-46EE-8DD6-7FDDC6998EE8@yahoo.com> <7d2a8e91-c78b-4207-a4ab-41056333bdd5@gmail.com> <86ldihqwal.fsf@peasant.salychev.org> <358ACE63-4FC7-451B-8002-D24B283FCB6D@gmail.com>
index | | previous in thread | raw e-mail
This is a multi-part message in MIME format.
--------------FqIWQgq1SVMXXUnKhKfqnz49
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
On 02/01/2026 03:23, Enji Cooper (yaneurabeya) wrote:
>> On Jan 1, 2026, at 5:47 AM, Dmitry Salychev<dsl@FreeBSD.org> wrote:
>>
>>
>> Paul Floyd<paulf2718@gmail.com> writes:
>>
>>
>>> 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.
>>
>> I second this. It might also be hard for me to distill the message's
>> essence which is frequently hidden behind a pile of details.
>
> I third this: more information isn’t necessarily better and there are different ways of capturing different information (maybe a blog or diary would be helpful for raw form ideas like that :)!). If something gets too noisy, I tune it out (and potentially miss some helpful information in the meantime). …
Earlier, I mentioned the constraints and very many peculiarities of email.
Above, quotation levels have broken.
In a thread elsewhere, a request for clarification (for additional
details) might break quotation levels and/or wrapping.
The subsequent details might additionally break quotation levels and/or
wrapping.
Distillation of a message = its essence. A subject line is essential, a
_good_ subject line is essential, and if the essence (the distillation
is) presented _as_ the subject line, the essential change of the subject
line will please some people, will displease others.
We can not please everyone.
Less information, succinctness, is not necessarily better. I could
share an example of succinctness that breaks all ground rules of the
FreeBSD Community Code of Conduct. My reason for not sharing here and
now is not mutual respect for the value of brevity.
FreeBSD-specific information that is blogged beyond the freebsd.org
domain pleases some people, displeases others.
Some of the people who are not pleased are absent from the less than
entirely public places where values such as centralisation are discussed.
--------------FqIWQgq1SVMXXUnKhKfqnz49
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
<div class="moz-cite-prefix">On 02/01/2026 03:23, Enji Cooper
(yaneurabeya) wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:358ACE63-4FC7-451B-8002-D24B283FCB6D@gmail.com">
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">On Jan 1, 2026, at 5:47 AM, Dmitry Salychev <a class="moz-txt-link-rfc2396E" href="mailto:dsl@FreeBSD.org"><dsl@FreeBSD.org></a> wrote:
Paul Floyd <a class="moz-txt-link-rfc2396E" href="mailto:paulf2718@gmail.com"><paulf2718@gmail.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">On 2026-01-01 07:19, Mark Millard wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">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?"
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
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.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
I second this. It might also be hard for me to distill the message's
essence which is frequently hidden behind a pile of details.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
I third this: more information isn’t necessarily better and there are different ways of capturing different information (maybe a blog or diary would be helpful for raw form ideas like that :)!). If something gets too noisy, I tune it out (and potentially miss some helpful information in the meantime). …</pre>
</blockquote>
<p><br>
</p>
<p>Earlier, I mentioned the constraints and very many peculiarities
of email. </p>
<p>Above, quotation levels have broken. </p>
<p>In a thread elsewhere, a request for clarification (for
additional details) might break quotation levels and/or wrapping. </p>
<p>The subsequent details might additionally break quotation levels
and/or wrapping. </p>
<p>Distillation of a message = its essence. A subject line is
essential, a _good_ subject line is essential, and if the essence
(the distillation is) presented _as_ the subject line, the
essential change of the subject line will please some people, will
displease others. </p>
<p>We can not please everyone. </p>
<p>Less information, succinctness, is not necessarily better. I
could share an example of succinctness that breaks all ground
rules of the FreeBSD Community Code of Conduct. My reason for not
sharing here and now is not mutual respect for the value of
brevity.</p>
<p>FreeBSD-specific information that is blogged beyond the
freebsd.org domain pleases some people, displeases others. </p>
<p>Some of the people who are not pleased are absent from the less
than entirely public places where values such as centralisation
are discussed. </p>
</body>
<lt-container></lt-container>
</html>
--------------FqIWQgq1SVMXXUnKhKfqnz49--
help