From: "Štěpán Němec" <stepnem@gmail.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: should the mail list be splitted resp. sub-tagged ?
Date: Tue, 04 Jan 2011 20:49:47 +0100 [thread overview]
Message-ID: <87vd245u04.fsf@gmail.com> (raw)
In-Reply-To: <87ei8s1qta.fsf@gnu.org> (Bastien's message of "Tue, 04 Jan 2011 19:12:17 +0100")
Bastien <bastien.guerry@wikimedia.fr> writes:
> Hi Štěpán,
>
> Štěpán Němec <stepnem@gmail.com> writes:
>
>> FWIW, I do. Having [Org] (or anything, really) prepended to the subjects
>> of _all_ mails coming from a list that is already uniquely identifiable
>> (e.g. by its address) has no information value altogether (unlike
>> [Babel], [PATCH] etc.) and only takes up the much precious Subject:
>> header space.
>
> Not that reducing the label from [Orgmode] to [Org] already seem to be a
> progress in the right direction :)
>
> Would you object having [Org] instead of [Orgmode]?
Well, I wrote "anything", so, yeah ;-) But I actually usually read the
list through Gmane, so I'm mostly unaffected (and Gnus can also strip
the list identifier automatically). I still find any kind of such
server-side mangling Evil (see also Robert Pluim's reply, most of which
I could just sign myself), but from Nick Dokos' reply I see that for
people putting all incoming mail into one single place and not able or
willing to do anything more than that it can have its uses, so, each to
their own I guess...
Thank you for consideration,
Štěpán
next prev parent reply other threads:[~2011-01-04 19:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 8:52 should the mail list be splitted resp. sub-tagged ? Torsten Wagner
2010-12-17 12:15 ` Andrew J. Korty
2010-12-17 14:00 ` Giovanni Ridolfi
2010-12-17 15:56 ` Nick Dokos
2010-12-17 17:28 ` Samuel Wales
2010-12-17 15:40 ` Nick Dokos
2010-12-17 18:21 ` William Gardella
2010-12-17 20:33 ` William Gardella
2010-12-17 21:16 ` Eric S Fraga
2010-12-18 12:09 ` Torsten Wagner
2011-01-04 15:19 ` Bastien
2011-01-04 17:39 ` Štěpán Němec
2011-01-04 18:12 ` Bastien
2011-01-04 18:31 ` Jeff Horn
2011-01-04 19:49 ` Štěpán Němec [this message]
2011-01-04 20:43 ` Nick Dokos
2011-01-04 18:52 ` Nick Dokos
2011-01-04 19:25 ` Robert Pluim
[not found] ` <rpluim@gmail.com>
2011-01-04 20:02 ` Nick Dokos
2011-01-05 8:15 ` Robert Pluim
2011-05-05 14:05 ` Applying style to a paragraph for HTML export Nick Dokos
2011-05-05 14:35 ` Jambunathan K
2011-01-05 9:13 ` should the mail list be splitted resp. sub-tagged ? Achim Gratz
2011-01-05 9:56 ` Robert Pluim
-- strict thread matches above, loose matches on Subject: below --
2011-05-05 9:37 Applying style to a paragraph for HTML export Robert Pluim
2011-05-05 12:05 ` Jambunathan K
2011-05-05 12:33 ` Robert Pluim
2011-05-05 12:45 ` Jambunathan K
2011-05-05 13:16 ` Robert Pluim
2011-05-05 12:51 ` Jambunathan K
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vd245u04.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).