ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Patrick Gundlach <pg@levana.de>
Subject: Feature request: Timestamps
Date: 23 Jun 2002 14:26:48 +0200	[thread overview]
Message-ID: <87k7oqi3jr.fsf@gundla.ch> (raw)

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 :)

Patrick

-- 
I'll fade into the darkness


             reply	other threads:[~2002-06-23 12:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-23 12:26 Patrick Gundlach [this message]
2002-06-23 22:15 ` Hans Hagen
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=87k7oqi3jr.fsf@gundla.ch \
    --to=pg@levana.de \
    /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).