From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] email etiquette
Date: Thu, 26 Mar 2020 21:41:13 +0000
Message-ID: <CAPweEDy4L2uNMvqz69S1jmWmDHaBAFHX6d7MKEenPjttysyzyw@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD4G8-OxL+h68iZaQOPch-+6rpuFUKWWhYGi9z-5JFE+sA@mail.gmail.com>
On Thu, Mar 26, 2020 at 9:25 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Thu, Mar 26, 2020, 12:43 Cole Poirier <colepoirier@gmail.com> wrote:
>
> > Sorry for this lapse in judgement Luke. I've been trying my best to
> > adhere to proper mailing list etiquette, and I've switched to using the
> > open source mail client Mailspring to allow me to make sure I'm sending
> > plaintext mail. But of course, this doesn't prevent me from slipping
> > into my old ways, so thank you for this reminder, I'll try very hard not
> > to do this again.
> >
>
> We're not like some of the Kernel mailing lists which will just block any
> mail with html,
yeah that one's fun. at least it warns you with a reject rather than
silent treatment. the reason they only accept plaintext is because
the key kernel developers have mail-filters which look for
git-format-patch messages. therefore you absolutely do not want
html-formatted crap. plus, on (literally) the world's largest
software project (by a long, long margin) it just pisses a *lot* more
people off.
> so you can still use the gmail client if you want, just
> remember to try to trim excessive context, avoid top-posting, and avoid
> using non-plaintext features.
>
> I'm currently writing this in the gmail app for android, in case you were
> wondering.
i'm also on gmail "m.gmail.com" in a web browser with "mobile tab"
set. sigh it defaults to html (with no option to set plaintext).
however - yes, i still always trim context.
it's just habit.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 16:04 [libre-riscv-dev] Setup automation scripts Cole Poirier
2020-03-25 16:18 ` Luke Kenneth Casson Leighton
2020-03-25 16:22 ` Cole Poirier
2020-03-26 4:14 ` Luke Kenneth Casson Leighton
2020-03-26 19:42 ` Cole Poirier
2020-03-26 21:25 ` [libre-riscv-dev] email etiquette Jacob Lifshay
2020-03-26 21:33 ` Cole Poirier
2020-03-26 21:41 ` Luke Kenneth Casson Leighton [this message]
2020-03-26 22:41 ` Hendrik Boom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPweEDy4L2uNMvqz69S1jmWmDHaBAFHX6d7MKEenPjttysyzyw@mail.gmail.com \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git