From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: Corwin Brust <corwin@bru.st>, Max Nikulin <manikulin@gmail.com>,
emacs-orgmode@gnu.org, Bastien <bzg@gnu.org>
Subject: Re: Suggestion: User-contributed use-cases on orgmode.org ?
Date: Fri, 17 Nov 2023 09:31:53 +0000 [thread overview]
Message-ID: <87y1ewbu9i.fsf@localhost> (raw)
In-Reply-To: <LV8P223MB09202F19C408C6CA8B0F7257A2B7A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM>
David Masterson <dsmasterson@gmail.com> writes:
>> FYI, WORG is listed in "Repositories" right at https://sr.ht/~bzg/org/
>
> I see no mention of "~bzg/org" in worg-about.
> ... I think my lack of
> experience for many years is showing -- I didn't think to click on the
> ~bzg/worg link which would've told me about ~bzg/org. I assumed the
> link was just telling me what to put on 'git clone'. Perhaps that
> should be explained a little more in worg-about.
I guess that you are confused about
It is made of numerous .org files that you can clone from https://git.sr.ht/~bzg/worg.
Would it help if we change it to
It is made of numerous .org files from https://git.sr.ht/~bzg/worg.
?
>> Or we might consider https://git.sr.ht/~bzg/woof to automatically update
>> WORG pages for appropriately marked mailing list threads.
>
> Hmm. That sounds most interesting becuase it command line driven.
> Perhaps a new mailing list should be created for this?
I don't think so. We intentionally keep Org mailing list as a single
place for all the discussions, not just Org development.
AFAIU, Bastien is firmly into this policy (CCing him in case if I
misunderstood).
--
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-11-17 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 5:09 Suggestion: User-contributed use-cases on orgmode.org ? David Masterson
2023-11-14 8:36 ` Russell Adams
2023-11-14 10:31 ` Max Nikulin
2023-11-15 2:16 ` David Masterson
2023-11-15 3:23 ` Corwin Brust
2023-11-16 2:56 ` David Masterson
2023-11-16 9:43 ` Ihor Radchenko
2023-11-17 5:13 ` David Masterson
2023-11-17 9:31 ` Ihor Radchenko [this message]
2023-11-17 18:26 ` David Masterson
2023-11-18 10:51 ` Ihor Radchenko
2023-11-18 19:18 ` David Masterson
2023-11-19 15:38 ` Bastien Guerry
2023-11-15 2:14 ` David Masterson
2023-11-15 13:33 ` Russell Adams
2023-11-16 2:58 ` David Masterson
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=87y1ewbu9i.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=corwin@bru.st \
--cc=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).