Nico R. wrote:
This is unfortunate, because when the subject can't be displayed
completely by the mail reader, most messages look pretty much the same
to me, example when there are replies to them:
"Re: [Linux From Scratch] #1715: bas..."
I suggest changing the subject prefixes to LFS, BLFS, ALFS etc. to
improve this.
While you started the subject a second adjust that could be made is
making the subject clearer that we are dealing with a bug here. Sure,
all of us know exactly what this subject line means and the #xyz
indicates a ticket ID to us.
It can be made more clear. And is the project name truly necessary in
the Subject header. We already know which project a ticket belongs to
based on the mailinglist it was sent to (this of course is me assuming
most everybody uses separate email folders to filter email into. If you
have all your LFS emails in one folder, than this topic distinction
would be preferably for those people).
Maybe a change that combines both and use the old Bugzilla Subject method:
[LFS Ticket #abc] Summary here
[BLFS Ticket #def] Summary here
and so forth.
such mails are sent base64-encoded, you don't want to do a "view
/var/mail/nico" to have a quick look at them when bash tells you that
you have new mails. ;-)
Playing devil's advocate here: how about 'mutt /var/mail/nico' rather
than 'view /var/mail/nico'?
right now, but AFAIK it should be possible to send UTF-8-encoded texts
with content-transfer-encoding quoted-printable. This would make more
sense here, since most (if not all) of the text is US-ASCII anyway. (And
if the standards didn't allow it, you could simply send US-ASCII instead
of UTF-8 where possible.)
What happens in cases where text is *not* US-ASCII and still sent with
the content-transfer-encoding set to quoted-printable? Maybe nothing
happens. I admit to knowing next to nothing about character sets in this
way.
--
Gerard Beekmans
/* If Linux doesn't have the solution, you have the wrong problem */
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
