From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Feature request: Timestamps
Date: Mon, 24 Jun 2002 00:15:56 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020624000808.034c0070@remote-1> (raw)
In-Reply-To: <87k7oqi3jr.fsf@gundla.ch>
At 02:26 PM 6/23/2002 +0200, Patrick Gundlach wrote:
>Hello ConTeXt hackers,
>
>I would like to suggest to make some changes:
>
>since some of the context files (the files in texmf/tex/context/base)
>change once in a while, it would be nice to see which of them have
>changed. The versioning info in the file should be updated according to
>the last modified timestamp (if ther are any changes within the macros
>or the doc only, of course).
>
>Then it would be nice to have a web page with all the file listed in
>base together with their timestap. it can be a simple 'grep':
>
>something like this:
>
>xtag-exp.tex:%D version=2001.08.20,
>xtag-ext.tex:%D version=2001.03.21,
>xtag-ini.tex:%D version=2000.12.20,
>xtag-map.tex:%D version=2000.12.20,
>xtag-mmc.tex:%D version=2000.12.20,
>xtag-mml.tex:%D version=2000.12.20,
>xtag-mmp.tex:%D version=2000.12.20,
>
>this would help to see if I need the newest beta, if i find a bug in
>context in a certain file. For example, I am just checking the
>core-itm for Idris, but I am note sure if the bug (if it is a bug) i
>have found is still in the newest beta. Before downloading the whole
>new cont-tmf.zip it would be nice if I could check a page on the web
>and see if there are any changes.
>
>Or put all your file into cvs and give us read-access :)
i admit that i need to adapt the dates (but since i seldom work at the top
of the file ...
Once i got out local infra structure updated (just installed yet another
server which does auto backup using secure rsync) i will khave a look at
it; one reason for not using a cvs repository (i would only use it as
repository for public context stuff since i hate the idea of all kind of
mess ending up in there) was that i was in the process of splitting up
context (i'm still not sure what happens when one removes a file). So,
there will be either a cvs or rsyncable archive (synced with our local web
server).
Another option is to auto-update the time stamps (ignoring comment lines)
which is what i already do with the main file.
So, it will happen (i will also provide a mechanism in texexec to use
multiple context trees in parallel)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-06-23 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-23 12:26 Patrick Gundlach
2002-06-23 22:15 ` Hans Hagen [this message]
2002-06-24 8:20 ` Patrick Gundlach
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=5.1.0.14.1.20020624000808.034c0070@remote-1 \
--to=pragma@wxs.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).