From: Bastien <bzg@altern.org>
To: Ivan Kanis <ivan.kanis@googlemail.com>
Cc: joakim@verona.se, Burton Samograd <burton@samograd.ca>,
help-gnu-emacs@gnu.org, Nic Ferrier <nferrier@ferrier.me.uk>
Subject: Re: Emacs user conference
Date: Sun, 09 Dec 2012 12:39:16 +0100 [thread overview]
Message-ID: <87vccbihej.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87fw3f7myq.fsf@kanis.fr> (Ivan Kanis's message of "Sun, 09 Dec 2012 07:34:37 +0100")
Hi Ivan,
Ivan Kanis <ivan.kanis@googlemail.com> writes:
> The next action is to decide when this will happen. I propose May, 15.
> Is that date agreeable with everyone?
I think the first action is to make sure *someone* is in charge
of coordinating. I can't volonteer for this right now. Can we
contact the person behind http://emacsconf.herokuapp.com/ and
ask him to confirm he's in charge?
> I think we should narrow the discussion to one mailing list. I think
> help-gnu-emacs@gnu.org is the best. Do you agree with me?
I do -- I removed the other lists.
--
Bastien
next prev parent reply other threads:[~2012-12-09 11:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 4:40 Emacs user conference Ivan Kanis
2012-12-07 5:57 ` Burton Samograd
2012-12-07 6:43 ` joakim
2012-12-07 14:02 ` Ivan Kanis
2012-12-07 19:58 ` Nic Ferrier
2012-12-08 18:33 ` Bastien
2012-12-09 6:34 ` Ivan Kanis
2012-12-09 11:39 ` Bastien [this message]
2012-12-09 20:57 ` Nic Ferrier
2012-12-09 21:19 ` Bastien
2012-12-10 21:00 ` Nic Ferrier
2012-12-10 7:18 ` Ivan Kanis
2012-12-10 20:58 ` Nic Ferrier
[not found] ` <mailman.14963.1355123922.855.help-gnu-emacs@gnu.org>
2012-12-11 23:54 ` David Combs
2012-12-08 19:13 ` joakim
2012-12-09 0:03 ` Nic Ferrier
2012-12-09 8:08 ` joakim
[not found] ` <mailman.14759.1354889046.855.help-gnu-emacs@gnu.org>
2012-12-11 23:38 ` David Combs
2012-12-11 23:48 ` David Combs
2012-12-14 17:56 ` Oleksandr Gavenko
2012-12-07 21:12 ` Richard Stallman
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=87vccbihej.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=burton@samograd.ca \
--cc=help-gnu-emacs@gnu.org \
--cc=ivan.kanis@googlemail.com \
--cc=joakim@verona.se \
--cc=nferrier@ferrier.me.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.