From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
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: Sat, 18 Nov 2023 11:18:28 -0800 [thread overview]
Message-ID: <LV8P223MB0920E3FD266039A1F2C331A7A2B6A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87pm071ghi.fsf@localhost> (Ihor Radchenko's message of "Sat, 18 Nov 2023 10:51:53 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>>> Would it help if we change it to
>>>
>>> It is made of numerous .org files from https://git.sr.ht/~bzg/worg.
>>>
>>> ?
>>
>> Perhaps:
>>
>> Follow the link https://git.sr.ht/~bzg/worg for information (including
>> cloning) on the WORG Git repository at SourceHut (https://sourcehut.org).
>
> I am not sure if I like it.
Ok. The more I look at it, the more I'm okay with it. I confused the
link to ~bzg/worg with an argument you would give to 'git clone', but
that's just me jumping to conclusions.
--
David Masterson
next prev parent reply other threads:[~2023-11-18 19:19 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
2023-11-17 18:26 ` David Masterson
2023-11-18 10:51 ` Ihor Radchenko
2023-11-18 19:18 ` David Masterson [this message]
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=LV8P223MB0920E3FD266039A1F2C331A7A2B6A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=bzg@gnu.org \
--cc=corwin@bru.st \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).