From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Daniel Fleischer <danflscr@gmail.com>,
emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Org site is down
Date: Mon, 06 Nov 2023 10:34:53 +0100 [thread overview]
Message-ID: <8734xjns1u.fsf@bzg.fr> (raw)
In-Reply-To: <878r7b44nr.fsf@localhost> (Ihor Radchenko's message of "Mon, 06 Nov 2023 09:22:48 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
>> It should be back now, please report any problem you may notice.
>
> There are still issues with some bugs not being closed despite my emails
> containing the trigger keywords. However, it looks similar to
> https://lists.sr.ht/~bzg/woof/%3C87ilhjiw7g.fsf%40localhost%3E, so I
> assume that I just need to wait until the problem is solved.
Yes, this is probably the error.
Did you manage to get other bugs close? or to add tasks and patches?
This will prove that the inbox monitoring works correctly.
--
Bastien Guerry
next prev parent reply other threads:[~2023-11-06 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 12:41 Org site is down Daniel Fleischer
2023-11-05 12:43 ` Bastien
2023-11-05 12:50 ` Ihor Radchenko
2023-11-05 12:51 ` Bastien
2023-11-05 16:15 ` Bastien Guerry
2023-11-06 9:22 ` Ihor Radchenko
2023-11-06 9:34 ` Bastien Guerry [this message]
2023-11-06 9:42 ` Ihor Radchenko
2023-11-06 12:55 ` Bastien Guerry
2023-11-11 9:46 ` Ihor Radchenko
2023-11-29 9:14 ` Bastien Guerry
2023-11-29 9:48 ` Ihor Radchenko
[not found] ` <87r0jvb55f.fsf@bzg.fr>
2024-05-04 13:46 ` [BUG] tracker.orgmode.org does not track anything since March 8, 2024 (was: Org site is down) Ihor Radchenko
2024-05-04 17:58 ` [BUG] tracker.orgmode.org does not track anything since March 8, 2024 Bastien Guerry
2024-05-06 11:11 ` Ihor Radchenko
2024-05-06 12:20 ` 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=8734xjns1u.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=danflscr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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).