From: Ihor Radchenko <yantar92@posteo.net>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: Org-mode <emacs-orgmode@gnu.org>, stardiviner <numbchild@gmail.com>
Subject: Re: Unclear where ob-spice.el is being maintained
Date: Fri, 25 Aug 2023 10:15:46 +0000 [thread overview]
Message-ID: <87v8d3fmwd.fsf@localhost> (raw)
In-Reply-To: <87jztk9rae.fsf@bernoul.li>
Jonas Bernoulli <jonas@bernoul.li> writes:
> In 2022 I changed Melpa to get ob-spice.el from
> https://repo.or.cz/ob-spice.git in response to
> https://github.com/melpa/melpa/issues/7872#issuecomment-1034945112.
The last discussion was back in 2020 https://list.orgmode.org/orgmode/CAL1eYuL8zzG-FdEedOVbvm1cfc8W6ajWFr7cthvgs8oWDwj+Qw@mail.gmail.com/
However, your reference is 2022.
So, unless Christopher has something to say,
https://repo.or.cz/ob-spice.git is the last known active maintenance
location. The last commit is 2022
https://repo.or.cz/ob-spice.git/shortlog, and includes more changes
compared to ob-spice version in org-contrib.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-08-25 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:25 Unclear where ob-spice.el is being maintained Jonas Bernoulli
2023-08-25 0:59 ` Christopher M. Miles
2023-08-29 22:59 ` Jonas Bernoulli
2023-08-30 1:28 ` Christopher M. Miles
2023-08-30 5:20 ` Ihor Radchenko
2023-08-30 7:46 ` Bastien Guerry
2023-08-30 16:56 ` Jonas Bernoulli
2023-08-31 8:21 ` Ihor Radchenko
2023-08-31 17:11 ` Bastien Guerry
2023-09-01 9:30 ` Ihor Radchenko
2023-08-25 10:15 ` Ihor Radchenko [this message]
2023-08-27 10:34 ` Jonas Bernoulli
2023-08-28 3:34 ` Christopher M. Miles
2023-08-29 23:02 ` Jonas Bernoulli
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=87v8d3fmwd.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jonas@bernoul.li \
--cc=numbchild@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.