emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Bastien Guerry <bzg@gnu.org>
Cc: ~theophilusx <theophilusx@git.sr.ht>, emacs-orgmode@gnu.org
Subject: Re: [PATCH worg 0/2] Cleanup of LoB file
Date: Sun, 19 Jun 2022 11:06:32 +1000	[thread overview]
Message-ID: <87czf57918.fsf@gmail.com> (raw)
In-Reply-To: <875yky5ayj.fsf@gnu.org>

Bastien Guerry <bzg@gnu.org> writes:

> ~theophilusx <theophilusx@git.sr.ht> writes:
>> These patches just perform some basic cleanup of the library-of-
>> babel.org file. It also moves a duplicate library-of-babel.org file into
>> the archive directory.  Note that I am working on a complete overhaul of
>> worg, which I will implement in a separate branch in my sourcehut clone
>> of the repo.
> Thank you very much!  I applied the patches on worg.
> I also added you as a contributor to https://git.sr.ht/~bzg/worg/ so
> that you can now push changes directly.

OK, thanks Bastien. Just out of interest, would you be able to send me a
copy of the nginx config for worg? I'm working on improving the build
process and I would like my local nginx to have a similar config. Also,
just in case there are changes which I think might improve the
experience from the server side, I would be good to know exactly what
the orgmode.org settings are. 

You can send that to me privately. It might even be worthwhile checking
it into the repository for reference. 

  reply	other threads:[~2022-06-19  1:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  1:46 [PATCH worg 0/2] Cleanup of LoB file ~theophilusx
2022-06-18  1:11 ` [PATCH worg 1/2] Move duplicate and obsolete LoB to archive ~theophilusx
2022-06-18  1:13 ` [PATCH worg 2/2] Update and cleanup of LoB file ~theophilusx
2022-06-18 13:59 ` [PATCH worg 0/2] Cleanup " Bastien Guerry
2022-06-19  1:06   ` Tim Cross [this message]
2022-06-19  6:44     ` Bastien

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:

  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=87czf57918.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@git.sr.ht \


* 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


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).