From: Ihor Radchenko <yantar92@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "Rudolf Adamkovič" <salutis@me.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)]
Date: Wed, 22 Jun 2022 12:11:53 +0800 [thread overview]
Message-ID: <87letp72wm.fsf@localhost> (raw)
In-Reply-To: <87v8st74at.fsf@gnu.org>
Bastien <bzg@gnu.org> writes:
>> https://todo.sr.ht/~emacs/emacs/2 could be somewhat useful.
>
> Yes, somewhat: but I'm not yet clear on the steps to set up a mirror.
>
> If anyone can guide me from A to Z, I'd be glad.
The discussion mentions some cron job.
Quick googling yielded
https://git.sr.ht/~janbaudisch/git-mirror
https://www.edwardthomson.com/blog/mirroring_git_repositories.html
https://dzone.com/articles/mirroring-git-changes-from-one-server-to-another-s
Also, we might try to setup the mirror job via builds.sr.ht, but AFAIK
there is no available periodic build trigger, and you may need to
request running the job via direct API request
(https://man.sr.ht/builds.sr.ht/graphql.md)
Hope it helps.
Best,
Ihor
next prev parent reply other threads:[~2022-06-22 4:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 9:12 [BUG] Info JS does not work [9.5.3 (release_9.5.3-467-g2bd34e @ /Users/salutis/src/org-mode/lisp/)] Rudolf Adamkovič
2022-05-02 10:08 ` Ihor Radchenko
2022-05-29 10:08 ` Bastien
2022-05-30 3:29 ` Ihor Radchenko
2022-05-31 6:51 ` Bastien
2022-06-12 11:50 ` Bastien
2022-06-14 4:20 ` Ihor Radchenko
2022-06-14 7:20 ` Bastien
2022-06-21 14:26 ` Ihor Radchenko
2022-06-22 3:41 ` Bastien
2022-06-22 4:11 ` Ihor Radchenko [this message]
2022-09-18 8:13 ` Bastien
2022-09-20 8:31 ` Ihor Radchenko
2022-09-20 9:01 ` Bastien
2022-09-20 9:26 ` Ihor Radchenko
2022-09-21 20:23 ` Tim Cross
2022-09-22 15:32 ` Bastien
2022-10-01 12:24 ` Bastien Guerry
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=87letp72wm.fsf@localhost \
--to=yantar92@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=salutis@me.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).