From: Mirek Kaim <mirek.kaim@outlook.com>
To: Glenn Morris <rgm@gnu.org>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: A way to communicate announcements to developers
Date: Mon, 8 Dec 2014 19:22:47 +0100 [thread overview]
Message-ID: <COL131-W67C6EA99568E34C1BBB22D84640@phx.gbl> (raw)
In-Reply-To: <krmw6yt63e.fsf@fencepost.gnu.org>
> From: rgm@gnu.org
> To: emacs-devel@gnu.org
> Subject: A way to communicate announcements to developers
> Date: Mon, 8 Dec 2014 12:16:21 -0500
>
>
> Please set up a mechanism to communicate important announcements
> (feature freezes, all documentation now to be in esperanto, that kind of
> thing) to developers. It's been discussed before but nothing ever
> happened. I still favour an emacs-devel Mailman "announce" topic, but
> anything will do, so please don't spend ages discussing the very best
> way. A web page to check, whatever.
>
> It's not reasonable to expect all developers to follow this (very noisy)
> list to get such information.
> (I'm considering disabling my subscription; I think I'd get more done.)
>
perhaps silly idea, but how about empty commits? just a message, and predefined - always the same - author.
devs can be expected to keep up with the source tree, so i guess it could work.
unic0rn
next prev parent reply other threads:[~2014-12-08 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 17:16 A way to communicate announcements to developers Glenn Morris
2014-12-08 18:22 ` Mirek Kaim [this message]
2014-12-08 18:24 ` Lars Magne Ingebrigtsen
2014-12-08 19:05 ` Stefan Monnier
2014-12-08 23:55 ` Stephen Leake
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=COL131-W67C6EA99568E34C1BBB22D84640@phx.gbl \
--to=mirek.kaim@outlook.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@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.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).