From: Tim Cross <theophilusx@gmail.com>
To: Noboru Ota <me@nobiot.com>
Cc: emacs-orgmode@gnu.org, Timothy <tecosaur@gmail.com>
Subject: Re: Introducing Org-transclusion
Date: Sat, 06 Nov 2021 21:22:49 +1100 [thread overview]
Message-ID: <877ddl7f06.fsf@gmail.com> (raw)
In-Reply-To: <87v915k2vm.fsf@nobiot.com>
Noboru Ota <me@nobiot.com> writes:
> Timothy <tecosaur@gmail.com> writes:
>> Hi Tim,
>>
>
>>> I feel it is functionality which will be used by a subset of users
>>> or by others only occasionally.
>
> Tim, thank you for your feedback.
> Timothy, thank you for forwarding Tim's feedback into the loop.
>
> I think this assessment is fair and reflects the current usage from the
> feedback I get.
>
>>> WRT making this part of org-mode core, I’m not in favour. This is no
>>> reflection on the package, which I think is a great addition to the org
>>> ecosystem. My preference would be for this package to be an add-on
>>> package in either ELPA or non-GNU ELPA.
>
> I will take this as the guidance and pursue ELPA as my first option. I
> have just signed and returned the FSF copyright assignment form.
>
> Now I will need to go and learn how to add a package to ELPA.
>
> Thank you.
> Noboru
Noboru,
thank you for making such a valuable contribution. I think your package
will be a valuable addition and it is great you have gone that extra
distance to sign the FSF copyright paperwork and are willing to do the
work to add it into ELPA.
I'm not 100% certain, but I think there is some information in the ELPA
git repository on how to setup and contribute a package to ELPA. Further
guidance can also be gained by asking on the emacs-devel mail list.
next prev parent reply other threads:[~2021-11-06 10:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 11:51 Introducing Org-transclusion Noboru Ota
2021-10-30 12:31 ` Juan Manuel Macías
2021-11-01 9:17 ` Noboru Ota
2021-10-30 13:59 ` Ihor Radchenko
2021-11-01 9:11 ` Noboru Ota
2021-11-01 13:24 ` Ihor Radchenko
2021-11-06 10:43 ` Noboru Ota
2021-11-08 15:07 ` Ihor Radchenko
2021-11-10 21:09 ` Noboru Ota
2021-11-14 8:22 ` Ihor Radchenko
2021-11-14 9:35 ` Ihor Radchenko
2021-11-01 20:07 ` Thomas Paulsen
2021-11-01 21:01 ` Noboru Ota
2021-11-02 5:17 ` Timothy
2021-11-05 19:53 ` Noboru Ota
2021-11-05 21:56 ` Tim Cross
2021-11-05 23:20 ` Timothy
2021-11-06 10:14 ` Noboru Ota
2021-11-06 10:22 ` Tim Cross [this message]
2021-11-06 11:49 ` Noboru Ota
2021-11-05 17:11 ` Uwe Brauer
2021-11-05 19:24 ` Noboru Ota
2021-11-05 20:15 ` Uwe Brauer
2021-11-05 23:02 ` Noboru Ota
2021-11-06 14:01 ` Uwe Brauer
2021-11-06 14:25 ` Ihor Radchenko
2021-11-06 14:54 ` Noboru Ota
2021-11-06 15:49 ` Uwe Brauer
2021-11-07 7:34 ` Ihor Radchenko
2021-11-07 8:07 ` Uwe Brauer
2021-11-07 8:30 ` Ihor Radchenko
2021-11-07 13:25 ` Uwe Brauer
2021-11-07 13:41 ` Ihor Radchenko
2021-11-07 13:56 ` Uwe Brauer
2021-11-05 19:59 ` Noboru Ota
2021-11-05 20:13 ` Uwe Brauer
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=877ddl7f06.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=me@nobiot.com \
--cc=tecosaur@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 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).