emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
To: "Andrew J. Korty" <ajk@iu.edu>
Cc: Org-mode ml <emacs-orgmode@gnu.org>
Subject: Re: should the mail list be splitted resp. sub-tagged ?
Date: Fri, 17 Dec 2010 15:00:41 +0100	[thread overview]
Message-ID: <83oc8kzegm.fsf@yahoo.it> (raw)
In-Reply-To: <91598.1292588125@iu.edu> (Andrew J. Korty's message of "Fri, 17 Dec 2010 07:15:25 -0500")

"Andrew J. Korty" <ajk@iu.edu> writes:

tags seems to be:

- [babel] [1] or [Babel] 
- [PATCH] 
- [PATCH n/m]
- [Accepted]  : means "patch accepted".
-  Bug:
- MobileOrg

acronym tags[2]:
[OT]
[RFC] 
and so on 

[1] http://lists.gnu.org/archive/html/emacs-orgmode/2009-11/msg00212.html
[2] http://www.gaarde.org/acronyms/

> Torsten Wagner <torsten.wagner@gmail.com> wrote:
>
>> Thinking of tags, I wonder why we use [Orgmode] since all mails
>> coming from emacs-orgmode(a)gnu.org which is a strong indicator
>> already.
>
> Not sure I agree with splitting the list, but the [Orgmode] tag is
> definitely superfluous.  Who has a mail client that can't filter on
> the List-Id field?

Come on! This is a standard for GNU project mailing lists:

[gnugo-devel] Gnugo and CGoban [3]

[coreutils] new snapshot available: coreutils-8.7.66-561f8 [4]

I think it will never change.

cheers,
Giovanni

[3] http://lists.gnu.org/archive/html/gnugo-devel/2010-12/index.html
[4] http://lists.gnu.org/archive/html/coreutils/2010-12/index.html

  reply	other threads:[~2010-12-17 13:59 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 [this message]
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
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=83oc8kzegm.fsf@yahoo.it \
    --to=giovanni.ridolfi@yahoo.it \
    --cc=ajk@iu.edu \
    --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).