From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Mon, 6 Aug 2001 12:35:45 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Test binaries of gcc-3.0.1 20010802 (prerelease)
Message-ID: <3B6E8F21.9731.4A3189@localhost>
References: <3B6E81AE DOT 11304 DOT 15A42C AT localhost>
In-reply-to: <Pine.SUN.3.91.1010806122552.24567B-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

On 6 Aug 2001, at 12:27, Eli Zaretskii wrote:

> > Maybe it would be best to create tag like v2_03_b in CVS and commit 
> > related changes (so one will be able to get original 2.03 from CVS
> > and also current updated version). Posting current relevant changes 
> > only tells current state as we may have something more after some
> > weeks.
> 
> I meant to post diffs against stock v2.03, not against the CVS.  If it 
> will help you build GCC 3.0.1 with such a patched library, that is.

I didn't talk about posting diffs against current CVS version. My idea
was to have a tag in CVS for current updated v2.03, so one who wants 
to get it can easily do that (eg. 'cvs get -r v2_03_b djgpp')

I would prefer that rather than simpy posted diffs against released 
v2.03 as they may become obsolete already after some weeks
and one will need to collect new patches from mailing list again.
For example I don't need Win2K related patches myself so I'm not 
following them to carefully and the same can be true also for others

Andris