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 09:43:06 -0400 [thread overview]
Message-ID: <CAC=rjb67BVQC8MM_rT1whUnzFxz-k1A2UrE0jkeW2-fZXKLmgQ@mail.gmail.com> (raw)
In-Reply-To: <874koce5n9.fsf@bzg.fr>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
It primarily adds features.
It fixes the problem reported here [1] but that's probably not a common
problem and the person who reported it probably already migrated.
[1] https://orgmode.org/list/87d05nidu1.fsf@iki.fi/
On Sat, Sep 5, 2020 at 9:04 AM Bastien <bzg@gnu.org> wrote:
> Hi Ian,
>
> ian martins <ianxm@jhu.edu> writes:
>
> > Sure, I'd be happy to maintain ob-java.
>
> Thanks! Does your work on ob-java.el fix bugs or does it foremost
> add new features? If the former, we can add it now to master, then
> add you as a maintainer immediately.
>
> > 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.
>
> Yes -- for now (< 9.4) we cannot accept changes in ob-core.el.
>
> Thanks,
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1695 bytes --]
next prev parent reply other threads:[~2020-09-05 13:43 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
2020-09-05 13:04 ` Bastien
2020-09-05 13:43 ` ian martins [this message]
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=rjb67BVQC8MM_rT1whUnzFxz-k1A2UrE0jkeW2-fZXKLmgQ@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).