From: "David O'Toole" <deeteeoh1138@gmail.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: For your consideration: Extending org-info-js with additional hooks
Date: Thu, 29 Dec 2022 12:32:48 -0500 [thread overview]
Message-ID: <CAAz1J51EmPrtbAGXVfPjY6x4FWP9H-8DkcNNf8VR4XNrKXYnrQ@mail.gmail.com> (raw)
In-Reply-To: <87k02akyp3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Ok, I will get started on this :)
On Thu, Dec 29, 2022 at 10:38 AM Bastien Guerry <bzg@gnu.org> wrote:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
> > Bastien, since the activity around org-info-js revived after a long
> > delay, should we move the code out of worg into a separate repo?
>
> Yes, definitely. David, would you like to set up a new repository
> with the code from the org-info-js directory here:
>
> https://git.sr.ht/~bzg/worg/tree/master/item/code/org-info-js
>
> You can try to excise the directoy while preserving its history,
> although I would not make it mandatory for org-info-js to live in
> a new, separate repository.
>
> Once this is done, we'll see how to remove org-info-js from Worg.
>
> Thanks!
>
> --
> Bastien
>
[-- Attachment #2: Type: text/html, Size: 1279 bytes --]
next prev parent reply other threads:[~2022-12-29 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 18:33 For your consideration: Extending org-info-js with additional hooks David O'Toole
2022-12-13 10:00 ` Ihor Radchenko
2022-12-13 16:32 ` David O'Toole
2022-12-13 17:20 ` David O'Toole
2022-12-14 15:40 ` David O'Toole
2022-12-29 15:38 ` Bastien Guerry
2022-12-29 17:32 ` David O'Toole [this message]
2023-08-05 9:25 ` Ihor Radchenko
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=CAAz1J51EmPrtbAGXVfPjY6x4FWP9H-8DkcNNf8VR4XNrKXYnrQ@mail.gmail.com \
--to=deeteeoh1138@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--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).