From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io
Subject: Re: [kernelci] Some suggestions and questions
Date: Thu, 13 Dec 2018 12:34:57 +0000 [thread overview]
Message-ID: <20181213123457.GF10669@sirena.org.uk> (raw)
In-Reply-To: <CADz3at1pRKih+JD2FerjgjKrU+p2RrnTfYoUadNAmXSi_Gp3UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Thu, Dec 13, 2018 at 07:14:34AM -0500, Mike Holmes wrote:
> Mobile
Desktop.
> On Thu, Dec 13, 2018, 6:49 AM Mark Brown <broonie@kernel.org wrote:
> > E-mail doesn't support hashtags though :(
> What extra support bis needed ?
> I assumed adding the tag to the subject was all E-mailed needed to support,
> it will then pull in all replies I think, but it has to be in the first
> message, but I am not an expert.
It'll get passed through but clients don't know to do anything with it,
you either get noise characters in the subject if people hashtag words
that are already there (which is a common way of doing these things),
it's less of an issue if they just get added to the end of the subject
line but still looks weird. It's like when people start randomly adding
@ to people's names in e-mail.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-13 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 21:38 Some suggestions and questions Dan Rue
2018-12-13 11:49 ` [kernelci] " Mark Brown
2018-12-13 12:14 ` Mike Holmes
2018-12-13 12:34 ` Mark Brown [this message]
2018-12-13 15:29 ` Dan Rue
2018-12-13 16:19 ` Mark Brown
2018-12-13 16:33 ` Dan Rue
2018-12-13 16:38 ` Mark Brown
[not found] ` <156FE20DF2374CC6.18828@groups.io>
2018-12-13 12:15 ` [kernelci] " Mark Brown
2018-12-14 18:00 ` Kevin Hilman
2018-12-14 18:06 ` Mark Brown
2018-12-14 21:51 ` Kevin Hilman
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=20181213123457.GF10669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernelci@groups.io \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox