From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] no recent message listed in the web interface
Date: Sun, 30 Apr 2023 15:47:00 +0200 [thread overview]
Message-ID: <4a3b6a27-d952-8f64-d937-5ec48a68bf72@gmx.es> (raw)
Dear list,
I‘m afraid that
https://mailman.ntg.nl/pipermail/ntg-context/2023/108157.html is the
most recent message displayed for 2023 in the web interface
(https://mailman.ntg.nl/pipermail/ntg-context/2023/date.html#108157).
Although the list has been distributing messages to subscribers and I
received them, I guess that the server software update might have
something to do with this.
Just for the record, I contacted Taco privately two weeks ago. No reply,
but I understand that obviously he is busy with other things.
Before sending him another message on the issue, I would like to ask
whether anyone could confirm that recent messages (from this week)
aren’nt being listed at
https://mailman.ntg.nl/pipermail/ntg-context/2023/date.html.
Many thanks for your help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2023-04-30 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 13:47 Pablo Rodriguez via ntg-context [this message]
2023-04-30 21:17 ` Jean-Pierre Delange via ntg-context
2023-05-01 7:35 ` Pablo Rodriguez via ntg-context
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a3b6a27-d952-8f64-d937-5ec48a68bf72@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox