From: Lennart Borgman <lennart.borgman@gmail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: The current rules for making Emacs binaries available on the net?
Date: Thu, 13 May 2010 15:40:39 +0200 [thread overview]
Message-ID: <AANLkTinFWDjT_M24AFOq0E8yG0Cv-GiyhN8wyk3GI_2Q@mail.gmail.com> (raw)
What are the rules now for publishing Emacs binaries from the
development sources? Is it sufficient to say that the are compiled
from the bazaar sources, or?
next reply other threads:[~2010-05-13 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 13:40 Lennart Borgman [this message]
2010-05-14 21:03 ` The current rules for making Emacs binaries available on the net? Richard Stallman
2010-05-14 22:51 ` Lennart Borgman
2010-05-15 20:27 ` Richard Stallman
2010-05-15 21:51 ` David Reitter
2010-05-16 6:38 ` Stephen J. Turnbull
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=AANLkTinFWDjT_M24AFOq0E8yG0Cv-GiyhN8wyk3GI_2Q@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@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).