Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.1830);
	 Thu, 1 Jun 2006 22:57:05 +0200
Received: by mail.proteosys.com (8.12.11.20060308/8.12.2) with ESMTP id k51KuxV6028000
	for <rainer.schoepf@PROTEOSYS.COM>; Thu, 1 Jun 2006 22:57:00 +0200
Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94])
	by relay.uni-heidelberg.de (8.13.4/8.13.1) with ESMTP id k51KrAAY030511
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 1 Jun 2006 22:53:10 +0200
Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94])
	by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id k51F09fB014566;
	Thu, 1 Jun 2006 22:52:56 +0200
Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 14.3) with
          spool id 1294846 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Thu, 1 Jun
          2006 22:52:55 +0200
Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de
          [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with
          ESMTP id k51KqtMg016115 for <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>;
          Thu, 1 Jun 2006 22:52:55 +0200
Received: from moutng.kundenserver.de (moutng.kundenserver.de
          [212.227.126.187]) by relay2.uni-heidelberg.de (8.12.10/8.12.10) with
          ESMTP id k51Kufvj018100 for <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>;
          Thu, 1 Jun 2006 22:56:41 +0200 (MET DST)
Received: from [84.169.181.48] (helo=morse.mittelbach-online.de) by
          mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis),
          id 0ML2ov-1Flu9r36p6-0003PF; Thu, 01 Jun 2006 22:52:43 +0200
Received: by morse.mittelbach-online.de (Postfix,
          from userid 501) id 27B7F46714; Thu,  1 Jun 2006 22:52:43 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <Pine.LNX.4.64.0604270936420.8277@bk-ng-05.proteosys>
            <20060427182251.GA23586@m0A023293.vpn.uni-freiburg.de>
            <20060530155648.GA16268@m0A023293.vpn.uni-freiburg.de>
            <20060531192925.GA7290@m0A023293.vpn.uni-freiburg.de>
X-Mailer: VM 7.19 under Emacs 21.3.1
X-Provags-ID: kundenserver.de abuse@kundenserver.de
              login:923c546e49b26a7485eda6910e23f403
Message-ID:  <17535.21403.129121.579232@morse.mittelbach-online.de>
Date:         Thu, 1 Jun 2006 22:52:43 +0200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Frank Mittelbach <frank.mittelbach@LATEX-PROJECT.ORG>
Subject: Re: LaTeX Release 2005/12/01
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <20060531192925.GA7290@m0A023293.vpn.uni-freiburg.de>
Precedence: list
X-ProteoSys-SPAM-Score: 0 () 
X-Scanned-By: MIMEDefang at proteosys.com
Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE
X-OriginalArrivalTime: 01 Jun 2006 20:57:05.0557 (UTC) FILETIME=[F06C2450:01C685BD]
Status: R
X-Status: 
X-Keywords:                  
X-UID: 4959

Heiko,

 > > * I have written a wrapper file that merges all the ltnews??.tex
 > >   documents: ltnews.pdf contain all LaTeX News issues 1--17.

I wonder if it is best to have the ltnews in there in cronological order or
better in reverse cronological order.

not even sure it is best to have them all together. most people will be only
interested in the latest information so reverse might be the best order

cheers
frank