From: Sietse Brouwer <sbbrouwer@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [***SPAM***] Updating Context or \"Never change a running System\"?
Date: Wed, 17 Apr 2013 17:17:43 +0200 [thread overview]
Message-ID: <CAF=dkzxH_gC1GDp2HH-OZOT-BPBVpdK0dBiS5s40hoy0ZO4Zjw@mail.gmail.com> (raw)
In-Reply-To: <516EA232.1060502@wxs.nl>
Hello Janis,
The closest you will get to a changelog, at the moment, is the git
mirror of the source:
http://repo.or.cz/w/context.git
That is not so useful if you want to know what new features have
arrived in the past year, but I thought I should mention it anyway.
I think one could also find a reasonable subset of feature
announcements by looking at e-mails to this list with the following
properties
* from:pragma@wxs.nl (that's Hans)
* "new in" OR "next beta" OR "new beta"
* after:2011-11-04
* (possibly: first in thread)
Unluckily, I can't convince my Gmail to search for that --- it ignores
the quotation marks, so I get buried in false positives.
Cheers,
Sietse
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-04-17 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 10:30 [***SPAM***] Updating Context or "Never change a running System"? Jan Heinen
2013-04-17 10:35 ` luigi scarso
2013-04-17 13:18 ` [***SPAM***] Updating Context or \"Never change a running System\"? Jan Heinen
2013-04-17 13:22 ` Hans Hagen
2013-04-17 15:17 ` Sietse Brouwer [this message]
2013-04-17 13:21 ` [***SPAM***] Updating Context or "Never change a running System"? Hans Hagen
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='CAF=dkzxH_gC1GDp2HH-OZOT-BPBVpdK0dBiS5s40hoy0ZO4Zjw@mail.gmail.com' \
--to=sbbrouwer@gmail.com \
--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).