From: ian martins <ianxm@jhu.edu>
To: Bastien <bzg@gnu.org>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: ob-java and ob-haxe
Date: Sat, 5 Sep 2020 07:34:31 -0400 [thread overview]
Message-ID: <CAC=rjb7KEqrFP=SOoNLzy_4RRA_gpxdoGgbrYtS52DcZw2XH=g@mail.gmail.com> (raw)
In-Reply-To: <87eenhq3aj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Bastien,
Sure, I'd be happy to maintain ob-java.
The drawback with keeping ob-haxe in an external repo is that the tests
won't run when org-mode is changed, but in practice its tests are very
similar to ob-java's so the actual risk of it being broken by a change will
be small if ob-java is in core.
I'll submit ob-haxe to GNU ELPA after ob-java has been accepted. That way I
can take out the common parts of ob-haxe which will have been incorporated
into ob-core.
On Fri, Sep 4, 2020 at 5:50 AM Bastien <bzg@gnu.org> wrote:
> Hi Ian,
>
> thanks for your work on this. Changes for ob-java.el should go in
> core after the 9.4 release. By the way, if you want to be ob-java.el
> maintainer, that'd be appreciated too!
>
> For ob-haxe.el, as Kyle suggests, let's prefer GNU ELPA (or upcoming
> Non-GNU ELPA): Elisp files in contrib/ will be exfiltrated after 9.4.
>
> Thanks,
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1346 bytes --]
next prev parent reply other threads:[~2020-09-05 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 11:56 ob-java and ob-haxe ian martins
2020-09-03 4:55 ` Kyle Meyer
2020-09-03 13:29 ` ian martins
2020-09-04 9:50 ` Bastien
2020-09-05 11:34 ` ian martins [this message]
2020-09-05 13:04 ` Bastien
2020-09-05 13:43 ` ian martins
2020-09-05 14:06 ` Bastien
2020-09-23 12:37 ` Bastien
2020-09-23 12:38 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC=rjb7KEqrFP=SOoNLzy_4RRA_gpxdoGgbrYtS52DcZw2XH=g@mail.gmail.com' \
--to=ianxm@jhu.edu \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@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/org-mode.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).