From: "Laurynas Biveinis" <lauras AT softhome DOT net>
Date: Sun, 13 May 2001 16:50:17 +0200
To: djgpp-workers AT delorie DOT com
Cc: JT Williams <jeffw AT darwin DOT sfbr DOT org>
Subject: Re: DJGPP 2.04 release date
Message-ID: <20010513165017.A331@lauras.lt>
Mail-Followup-To: djgpp-workers AT delorie DOT com,
	JT Williams <jeffw AT darwin DOT sfbr DOT org>
References: <20010513145204 DOT A379 AT lauras DOT lt> <Pine DOT SUN DOT 3 DOT 91 DOT 1010513155522 DOT 15149A-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.15i
In-Reply-To: <Pine.SUN.3.91.1010513155522.15149A-100000@is>; from eliz@is.elta.co.il on Sun, May 13, 2001 at 03:57:23PM +0300
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > I don't have my semifinished alias list right here, right now, but
> > I recall that there was little possible automation.
> 
> This is a misunderstanding: tarchange.lst is always created when djtar 
> cannot unpack the the archive without conflicts.  The mapping of the 
> problematic files is something you need to supply yourself; I didn't mean 
> to say that I have some magic which does that automatically.

Right, and I was talking about copious problematic files from the 
beginning.

Laurynas