Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Jun 2020 16:21:52 +0200
From:      Chris Knipe <savage@savage.za.org>
To:        Aryeh Friedman <aryeh.friedman@gmail.com>
Cc:        "Steve O'Hara-Smith" <steve@sohara.org>, Polytropon <freebsd@edvax.de>,  FreeBSD - <freebsd-questions@freebsd.org>
Subject:   Re: Mailing List Etiquette was freebsd vs. netbsd
Message-ID:  <CA+4TWFskS-+PbEM2bUK+5mjTWv=ZsSLnbpCm4OQ3WLWwoE6HYA@mail.gmail.com>
In-Reply-To: <CAGBxaXkyAr=EmFkGed9SbLqNBfzuTuZJkWsKm=q=hjMjUSix9Q@mail.gmail.com>
References:  <20200613154409.GA89618@neutralgood.org> <13115.1592302784@segfault.tristatelogic.com> <20200616071153.00006f4d@seibercom.net> <CA+4TWFuWN1BV=FftC1xNCYRgqwX+Cb=wMg_L9MxFHx17Nzjm5Q@mail.gmail.com> <20200616075548.000066f1@seibercom.net> <20200616140416.bd7b8bf2.freebsd@edvax.de> <CA+4TWFtgaMkJWAOuvEpSg2TOo2hrG-P7EHJUigCQwgQw3iXtWQ@mail.gmail.com> <20200616142043.7d599458.freebsd@edvax.de> <CA+4TWFvf7w=4djQfWLtXhqmip0Rb72Js6BbOW=F_gUkufXuQFw@mail.gmail.com> <20200616144141.6203d978e9bd43418b17dcbc@sohara.org> <CA+4TWFsCcegZN7L0CGzJ1PFinROmRy1ypZ6mxF59zDeXHh2C=A@mail.gmail.com> <CAGBxaX=GZ-PRYJT_n+XpqRHmsFwGq58tSF0emqCJ__ioot7Lpw@mail.gmail.com> <CA+4TWFu5_aPENk6W3Pm6dQhT4DDCFM3XnQ_2en7yeGad1k15WA@mail.gmail.com> <CAGBxaXkyAr=EmFkGed9SbLqNBfzuTuZJkWsKm=q=hjMjUSix9Q@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Tue, Jun 16, 2020 at 4:06 PM Aryeh Friedman <aryeh.friedman@gmail.com>
wrote:

> Simple - don't email it. If you do, attach it as an attachment (MIME is
>> there for a reason)...
>>
>> There's GIT / CVS / Take your pick for a reason... :-)
>>
>
> If you don't like email then you should not be using FreeBSD because for
> better or worse the community has standardized on email as the primary tech
> support venue and thus absolutely needs to have something that can be used
> to give tech support (including 100% accurate cut and pasting).
>

And again - there's absolutely -nothing- wrong with that at all, I never
said that there was... Millions of companies provide support to millions of
users every day using email... That being said, I get a 80 character plain
text email from a company as "support," I deem that as unprofessional, and
the email will more than likely just be deleted.  We live in modern times,
unfortunately.  Presentation matters, whether you like it or not.

Cut & paste from the attachment, then you won't have any formatting issues
from any MUAs, but I guess it's too much effort to open the attachment.
There's plenty of solutions (UUEncode/BASE64, as you so nicely put it, has
also been trialed and tested over many, many years, just FYI - it also has
the benefit of < 80 characters wide), 80x25 is not one of them, and whether
you like it or not, you will -never- get the world to adhere to a 80 (or 74
or whatever) character wide email. The world has moved on, deal with it.

The fact is, you should be committing your code to a repository, and
checking said code out of said repository when you need it. In an open
source environment, said code is also publicly viewable using any half
decent web browser (I guess GITHUB is also doing it wrong?)  No, code
should not be shared via email - and if you do then so be it - your choice,
not a requirement. You don't need to email the code, all you can do is
email a URL to your commit / diff... Again, too much effort to open a URL
right?  I forgot that in the old days without GUIs, we couldn't even double
click.  I guess you still can't today.

Again, it's the minority that is sharing code via email... In fact, I would
say very, very, very little people do it.

Oh - and I love email.... Never said I didn't.

-- 

Regards,
Chris Knipe



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?CA+4TWFskS-+PbEM2bUK+5mjTWv=ZsSLnbpCm4OQ3WLWwoE6HYA>