emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julien Danjou <julien@danjou.info>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Splitting mailing list
Date: Sun, 27 Feb 2011 15:09:04 +0100	[thread overview]
Message-ID: <871v2td0xr.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <87pqqdprxe.fsf@altern.org> (Bastien's message of "Sun, 27 Feb 2011 12:43:59 +0100")


[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]

On Sun, Feb 27 2011, Bastien wrote:

> I am in favor of using a [DEV] tag and stick to one single list.

This is not something automatic, so this is not something everyone will
do. I won't think about it most of time and will forget, so…

> The path from users to developers (and to core Org developers) is
> a continuum, keeping this continuum on one list is a good thing.

Your own vision of Org is probably that, so you'd subscribe to both
list. I personally do not have enough time to care about users problems
nor their features complaints for now, so spending time with
developement subject only and not having to filter out usage related
thread would make me gain an amount of time that I could spend on
hacking Org.

This is not something I'd propose on a low trafic list, but the number
of mails here is getting bigger and bigger, and it's hard for me as a
developer (and not as a maintainer like you) to just follow the stream
of subject I am interested into (i.e. developement of Org).

If some developers (like you) have more time to follow users subjects,
nothing stop you to read both lists.

At this point of trafic rate, not splitting is mostly killing people
like me. :)

-- 
Julien Danjou
❱ http://julien.danjou.info

[-- Attachment #1.2: Type: application/pgp-signature, Size: 835 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2011-02-27 14:09 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-27 10:30 Splitting mailing list Julien Danjou
2011-02-27 11:43 ` Bastien
2011-02-27 14:09   ` Julien Danjou [this message]
2011-02-27 14:19     ` Gour
2011-02-27 14:22   ` Matthew Sauer
2011-02-27 20:49   ` Alan L Tyree
2011-02-27 22:53     ` Andrew J. Korty
2011-02-28  0:15       ` Alan L Tyree
2011-02-28  0:21         ` Matthew Sauer
2011-02-28 20:43           ` Eric S Fraga
2011-02-28  8:48         ` Julien Danjou
2011-02-28  9:48           ` Alan Tyree
2011-02-28  2:38       ` Nick Dokos
2011-02-28 10:46       ` Bastien
2011-02-28 12:12         ` Julien Danjou
2011-02-28 12:44           ` Bastien
2011-02-28 12:58             ` Jambunathan K
2011-02-28 14:14             ` Julien Danjou
2011-02-28 16:14             ` Nick Dokos
2011-02-28 17:12               ` John Hendy
2011-03-01 11:50               ` Bastien
2011-02-27 21:20   ` Jeff Horn
2011-02-27 21:26     ` Jeff Horn
2011-02-27 22:20       ` Samuel Wales
2011-02-28 10:49         ` Bastien
2011-02-28 15:03           ` Ian Barton
2011-02-28 17:05           ` Samuel Wales
2011-02-28 20:17             ` Konrad Hinsen
2011-02-27 16:23 ` Chris Thompson
2011-02-27 16:56   ` Julien Danjou
2011-02-28  9:50 ` Torsten Wagner
2011-02-28 11:02   ` Let's stick to one list for now (was: Splitting mailing list) Bastien
2011-02-28 11:34     ` Let's stick to one list for now Julien Danjou
2011-02-28 17:06       ` Eric Schulte
2011-02-28 17:09         ` Automatic Org-mode mailing list signature -- Was: [O] " Eric Schulte
2011-02-28 18:14           ` Automatic Org-mode mailing list signature -- Was: " Nicolas
2011-02-28 18:58             ` Eric Schulte
2011-03-01  4:30           ` Automatic Org-mode mailing list signature -- Was: [O] " theo
2011-03-02 17:35           ` Bastien
2011-03-02 17:54             ` Eric Schulte
2011-03-02 18:22             ` Automatic Org-mode mailing list signature -- Was: " Nicolas
2011-03-02 18:51               ` theo
2011-03-03  8:25               ` Bastien
2011-03-03  8:36                 ` Gregor Zattler
2011-03-03 13:49                 ` Eric S Fraga
2011-03-03 14:01                   ` Bernt Hansen
2011-03-03 15:09                 ` Julien Danjou
2011-03-03 15:12                   ` Carsten Dominik
2011-03-03 16:33                 ` Bastien
2011-03-03 17:02                 ` Achim Gratz
2011-03-03 17:53                 ` Nick Dokos
2011-03-04  9:57                   ` Julien Danjou
2011-03-02 21:44             ` Automatic Org-mode mailing list signature -- Was: [O] " Achim Gratz
2011-03-02 22:59               ` suvayu ali
2011-03-03  8:23               ` Bastien
2011-02-28 17:53       ` Dan Davison
2011-02-28 18:10         ` Jambunathan K
2011-02-28 20:23         ` Jeff Horn
2011-03-01 11:55           ` Bastien

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=871v2td0xr.fsf@keller.adm.naquadah.org \
    --to=julien@danjou.info \
    --cc=bzg@altern.org \
    --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).