From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Glenn Morris'" <rgm@gnu.org>
Cc: help-emacs-windows@gnu.org, 'Sean Sieger' <sean.sieger@gmail.com>,
'Emacs development discussions' <emacs-devel@gnu.org>
Subject: RE: New build of the trunk for MS Windows
Date: Mon, 22 Oct 2012 13:11:40 -0700 [thread overview]
Message-ID: <6FB12C4CB1654ED0B1A7EF8D4C53799A@us.oracle.com> (raw)
In-Reply-To: <jwvr4oq9uo1.fsf-monnier+emacs@gnu.org>
> > It would be great it someone would do for MS Windows what these
> > guys (and probably others) do for other platforms:
> >
> > http://emacsformacosx.com/
> > http://emacs.naquadah.org/
> > which is just make builds on a regular basis and stick them
> > on a website somewhere. No need to let the development list
^^^^^^^^^^^
> > know every time.
>
> Someone used to do that, IIRC (uploaded to alpha.gnu.org).
Sean Sieger did it. But he also notified emacs-devel and help-emacs-windows.
I think the notifications are important, especially if the updates are not
regular.
It is most important to notify help-emacs-windows@gnu.org, IMO. That would be
enough, I think, if you are worried about Emacs Dev being annoyed by the
announcements. These are announcements for Emacs users, not just for
developers.
Ccing help-emacs-windows@gnu.org. (You should not drop that list from the cc
list if you are discussing a proposal to stop sending such messages.)
next prev parent reply other threads:[~2012-10-22 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 18:11 New build of the trunk for MS Windows Dani Moncayo
2012-10-22 18:38 ` Dani Moncayo
2012-10-22 18:52 ` Glenn Morris
2012-10-22 19:20 ` Dani Moncayo
2012-10-22 19:25 ` Stefan Monnier
2012-10-22 19:58 ` Deniz Dogan
2012-10-22 20:11 ` Drew Adams [this message]
2012-10-27 15:30 ` Christoph Scholtes
2012-10-27 15:58 ` Noah Lavine
2012-11-08 9:31 ` Eric Lilja
2012-11-08 19:04 ` Glenn Morris
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=6FB12C4CB1654ED0B1A7EF8D4C53799A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.org \
--cc=sean.sieger@gmail.com \
/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.