ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: root@ntg.nl (Cron Daemon)
To: ntg-context@ntg.nl
Subject: [NTG-context] Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
Date: Fri, 16 Aug 2024 16:01:13 +0200 (CEST)	[thread overview]
Message-ID: <20240816140113.5523D484F64@cgl.ntg.nl> (raw)

receiving incremental file list
 ./
 ctan.lsr
 document-2.htm
 download-1.htm
 download-2.htm
 logo-ade.png
 logo-cts.png
 logo-pod.png
 rss.xml
 show-fil.pdf
 context/latest/
 context/latest/cont-lmt.zip
 context/latest/cont-mpd.zip
 context/latest/cont-ppc.zip
 context/latest/cont-sci.zip
 context/latest/cont-tmf.zip
 context/latest/cont-tst.7z
 context/latest/cont-tst.tar.xz
 context/latest/cont-tst.zip
 
 sent 187,925 bytes  received 40,189,993 bytes  3,511,123.30 bytes/sec
 total size is 617,576,475  speedup is 15.29


Running archiver:

New dir: /var/www/aanhet.net/context//htdocs/archives/context-2024-08-16.16
271978560	/var/www/aanhet.net/context//htdocs/archives/context-2024-08-16.16/latest
126745317	/var/www/aanhet.net/context//htdocs/archives/context-2024-08-16.16/current
398727973	/var/www/aanhet.net/context//htdocs/archives/context-2024-08-16.16
398727973	total
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2024-08-16 14:03 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 14:01 Cron Daemon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-01 19:01 Cron Daemon
2024-10-31 12:01 Cron Daemon
2024-09-25 10:01 Cron Daemon
2024-09-17 12:01 Cron Daemon
2024-08-16 15:01 Cron Daemon
2024-08-13 14:01 Cron Daemon
2024-07-31 18:01 Cron Daemon
2024-06-21 22:01 Cron Daemon
2024-06-21 18:01 Cron Daemon
2024-06-18 21:01 Cron Daemon
2024-06-16 18:01 Cron Daemon
2024-06-14  8:01 Cron Daemon
2024-05-31 19:01 Cron Daemon
2024-05-27 17:01 Cron Daemon
2024-05-17 15:01 Cron Daemon
2024-05-16 12:01 Cron Daemon
2024-05-16 11:01 Cron Daemon
2024-05-16 10:01 Cron Daemon
2024-05-16  9:01 Cron Daemon
2024-05-16  8:01 Cron Daemon
2024-05-13 19:01 Cron Daemon
2024-05-11 11:01 Cron Daemon
2024-04-01  8:01 Cron Daemon
2024-03-11 10:01 Cron Daemon
2024-03-05 12:01 Cron Daemon
2024-02-27  9:01 Cron Daemon
2024-02-22 18:01 Cron Daemon
2024-02-22  3:01 Cron Daemon
2024-02-22  2:01 Cron Daemon
2024-02-20 17:03 Cron Daemon
2024-02-14 13:01 Cron Daemon
2024-02-14 12:01 Cron Daemon
2024-02-14 10:01 Cron Daemon
2024-01-24 22:01 Cron Daemon
2024-01-23 10:01 Cron Daemon
2024-01-20  9:01 Cron Daemon
2024-01-18  0:01 Cron Daemon
2024-01-08 11:01 Cron Daemon
2024-01-02 16:01 Cron Daemon
2024-01-02 11:01 Cron Daemon
2023-12-18  8:01 Cron Daemon
2023-12-18  7:01 Cron Daemon
2023-10-03  5:01 Cron Daemon
2023-09-26 17:01 Cron Daemon
2023-09-18 20:01 Cron Daemon
2023-09-18 16:01 Cron Daemon
2023-09-17  8:01 Cron Daemon
2023-09-04 18:01 Cron Daemon
2023-09-03 18:01 Cron Daemon
2023-08-27 12:01 Cron Daemon
2023-08-23  7:03 Cron Daemon
2023-08-23  6:03 Cron Daemon
2023-08-23  5:03 Cron Daemon
2023-08-23  4:03 Cron Daemon
2023-08-16 18:01 Cron Daemon
2023-08-16  9:01 Cron Daemon
2023-08-15 18:01 Cron Daemon
2023-08-10 15:01 Cron Daemon
2023-08-09 16:01 Cron Daemon
2023-08-08 20:01 Cron Daemon
2023-08-08 15:03 Cron Daemon
2023-07-29 13:01 Cron Daemon
2023-07-28 19:01 Cron Daemon
2023-07-27 17:01 Cron Daemon
2023-07-26  0:03 Cron Daemon
2023-07-25 18:01 Cron Daemon
2023-07-18 21:01 Cron Daemon

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=20240816140113.5523D484F64@cgl.ntg.nl \
    --to=root@ntg.nl \
    --cc=ntg-context@ntg.nl \
    /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;
as well as URLs for NNTP newsgroup(s).