From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: emacs-26 3fc05cf: Scripts to automate windows binary distribution
Date: Wed, 25 Oct 2017 17:08:01 +0200 [thread overview]
Message-ID: <87y3nzgt9q.fsf@wanadoo.es> (raw)
In-Reply-To: 87inf3l1cm.fsf@gmx.de
Michael Albinus <michael.albinus@gmx.de> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> I don't see a problem to have scripts in Python under admin/. That
>> stuff is not for the users, it's mainly for Emacs maintainers, so the
>> tools it requires are less important.
>
> Could we document, which languages are accepted there? Let's start with
> Bash (or any POSIX shell), Guile, Perl, Python. Otherwise, somebody
> might contribute Lua scripts, or whatever.
What's wrong with Lua? :-)
IMHO, on this case, where a maintainer just puts on the repo the scripts
he wrote for his tasks, it is ok to accept the language that the
contributor decides. If those scripts where meant for users, then indeed
we should decide what's more convenient.
next prev parent reply other threads:[~2017-10-25 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171024173456.23065.52677@vcs0.savannah.gnu.org>
[not found] ` <20171024173457.C45BE2031F@vcs0.savannah.gnu.org>
2017-10-25 7:27 ` emacs-26 3fc05cf: Scripts to automate windows binary distribution Michael Albinus
2017-10-25 8:37 ` Phillip Lord
2017-10-25 10:16 ` Michael Albinus
2017-10-25 10:53 ` Kaushal Modi
2017-10-25 11:06 ` Michael Albinus
2017-10-25 14:44 ` Eli Zaretskii
2017-10-25 14:59 ` Michael Albinus
2017-10-25 15:08 ` Óscar Fuentes [this message]
2017-10-25 15:19 ` Eli Zaretskii
2017-10-25 15:27 ` Michael Albinus
2017-10-25 11:03 ` Noam Postavsky
2017-10-25 15:42 ` Phillip Lord
2017-10-25 12:11 ` Stefan Monnier
2017-10-25 15:45 ` Phillip Lord
2017-10-26 3:42 ` 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=87y3nzgt9q.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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 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.