emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Christopher M. Miles" <numbchild@gmail.com>,
	 Jonas Bernoulli <jonas@bernoul.li>,
	 Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Unclear where ob-spice.el is being maintained
Date: Wed, 30 Aug 2023 09:46:47 +0200	[thread overview]
Message-ID: <871qfl9dlk.fsf@bzg.fr> (raw)
In-Reply-To: <87il8xhzrf.fsf@localhost> (Ihor Radchenko's message of "Wed, 30 Aug 2023 05:20:52 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> "Christopher M. Miles" <numbchild@gmail.com> writes:
>
>> Thanks, Updated now.
>>> ...
>>>> 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.
>>>>>
>>>>> But org-contrib still contains that file and the README at the new
>>>>> location still contains
>
> Bastien, it looks like we can now remove ob-spice from org-contrib.
> Please, confirm.

I do, thanks.

-- 
 Bastien Guerry


  reply	other threads:[~2023-08-30  7:47 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 [this message]
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
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

  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=871qfl9dlk.fsf@bzg.fr \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jonas@bernoul.li \
    --cc=numbchild@gmail.com \
    --cc=yantar92@posteo.net \
    /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).