From: "Mark Brown" <broonie@kernel.org>
To: Dan Rue <dan.rue@linaro.org>
Cc: kernelci@groups.io
Subject: Re: Some suggestions and questions
Date: Thu, 13 Dec 2018 16:38:14 +0000 [thread overview]
Message-ID: <20181213163814.GS10669@sirena.org.uk> (raw)
In-Reply-To: <20181213163341.qf4u3sfazfeb2o7w@xps.therub.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Thu, Dec 13, 2018 at 10:33:41AM -0600, Dan Rue wrote:
> On Thu, Dec 13, 2018 at 04:19:50PM +0000, Mark Brown wrote:
> > If we're going to do it could we do it with a #minutes at the end of the
> > subject instead so that it doesn't disrupt the actual subject?
> > Since people read more by pattern matching the shapes of text than by
> > parsing out the individual letters (particularly when reading at speed)
> > it's not great to have them in the middle of text, this works a lot
> > better in systems that support hashtags since they tend to provide
> > visual cues that this isn't a normal word and even there outside of
> > Twitter with its severe length restrictions they normally get pushed to
> > a separate bit after the real text (Instagram used to encourage people
> > to put them in comments, not even in the actual post).
> Yea, good point. How's this specifically:
> Subject: Weekly Meeting 2018-12-10 #minutes
Sure.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-13 16:38 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
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 [this message]
[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=20181213163814.GS10669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dan.rue@linaro.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