public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Walters <cjw2004d@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: K
Date: Sun, 13 Jul 2008 17:36:18 -0400	[thread overview]
Message-ID: <487A7552.7020108@comcast.net> (raw)
In-Reply-To: <200807132118.21261.michaelkintzios@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Mick wrote:
| On Sunday 13 July 2008, felix@crowfix.com wrote:
|> On Sun, Jul 13, 2008 at 10:40:08AM -0700, maxim wexler wrote:
|>> I would like to raise my voice against the use of overly long subject
|>> lines that run out of space on the line provided.
|>>
|>> Complete sentences are not necessary. A few, well chosen words should
|>> suffice and spare the user the nuisance of opening mail that ultimately
|>> is of no value to him.
|
| Sorry!  Couldn't resist. ;-)
|
| I had a guy working for me who used to write the whole bl**dy email in the
| frigging Subject: field!  Arrrrgh!  When I asked him why didn't he use the
| body of the message like 'normal' people do, he argued that he intended
| saving me the time of opening the message to read it.  Sometimes you just
| can't win.
|
| Anyway, as others asked - how long is too long for this purpose?

LOL!  On another list once, someone posted the whole message in the subject
line, and again in the body of the message.  It was an error, and he
apologized, but your story there reminded me of that...

IMO, I haven't seen too many overly long subject lines, but I have seen several
overly short ones.  There has to be a Happy Medium (tm) out there.  Once we
find one, we can just ask our questions of her... lol! ;)

Regards,
Chris
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJIenVOAAoJEIAhA8M9p9DA9qMP/R9ayq2z7u3MvsT62Eux5ixG
Co5rV8yX0cO2UhwDostFShBVHzJ4L/Mem0ECUqrY+hznSdiz0LADyJV4bUpQpTqo
IaxcTF2CpXxp5Ozqk0D4DTwqPzqt/KxhRK87elS94KRp8b4G5VWXvgq14s5KlMRQ
TBCzwp6crLSNbczMr10vUxlQfthbcBhHkq7bfV9x2ByBCdbRT8Pv7lDVuLUm6oiy
CcxyxiKnviDGIH5BIWoTcPBB0NPKhavo0913kWe+eU4CDi/ANGqneMP+ao1kJf7M
rlgXoxBnIp/GXnSx/G1AdAhifMVTxBZ36lrmLnsOrz1yFMRZt+vwvCU91Dm8QMtq
G7Xr7W7BVcp2xwnrRyMqez4fSbdPZuJ9NUamddwHe4tOC2B0KrWuRXzRZZB1/3Rh
Im8xKAJApXk8w+vtPXgOo8qSKiTupHpJnCbHJ7QuoApCLAPzMm9OV130N+C8tWzZ
Igwe2MFzFFF3IyMuwugtpz/1VdFiPoKSuvkGDrlULoxFiTySS6UKLKTjC1qqoHBM
Lhu7r/GY7TSAUjc4puanjniCDF7ewE54e4UcllQPJh+V7ARvNEcSw5YW8PwYe7Ff
jXtM75CTqn+UnVsF+xEKLPiSo8r8qIED5HTfjwTFMmEgerlXagM72wSr8etio6Ku
D6gcxV6W2yp94QQI/oQa
=5x72
-----END PGP SIGNATURE-----
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-07-13 21:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13 17:40 [gentoo-user] proper subject lines maxim wexler
2008-07-13 18:32 ` Volker Armin Hemmann
2008-07-13 18:44   ` Dale
2008-07-13 20:17     ` b.n.
2008-07-15 18:13   ` maxim wexler
2008-07-13 19:23 ` felix
2008-07-13 19:40   ` Neil Bothwick
2008-07-13 20:18   ` [gentoo-user] OK Mick
2008-07-13 21:36     ` Chris Walters [this message]
2008-07-14 17:11     ` Alan McKinnon
2008-07-14 18:14       ` Willie Wong
2008-07-20 16:54         ` [gentoo-user] proper subject lines Mick

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=487A7552.7020108@comcast.net \
    --to=cjw2004d@comcast.net \
    --cc=gentoo-user@lists.gentoo.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
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