Message-ID: <20010210154816.710.qmail@lauras.lt>
From: "Laurynas Biveinis" <lauras AT softhome DOT net>
Date: Sat, 10 Feb 2001 17:48:16 +0200
To: djgpp-workers AT delorie DOT com
Subject: Re: Cygnus tree in SFN, again
Mail-Followup-To: djgpp-workers AT delorie DOT com
References: <20010210115707 DOT 1224 DOT qmail AT lauras DOT lt> <CAEGKOHJKAAFPKOCLHDIGEHCCAAA DOT tim DOT van DOT holder AT pandora DOT be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
In-Reply-To: <CAEGKOHJKAAFPKOCLHDIGEHCCAAA.tim.van.holder@pandora.be>; from tim.van.holder@pandora.be on Sat, Feb 10, 2001 at 03:22:55PM +0100
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


> a) If there are 8.3 conflicts (ie foobar123.c and
>    foobar123-xyzzy.c both exist), you should submit a
>    patch to the maintainers to get this fixed. Even if
>    it won't get accepted, you need to make sure they
>    know about the problem. 

The odds are they would laugh at me. Also some 8.3 names
are very ugly.

> b) Can't you use fnchange.lst to use 'NUL' as new name
>    for the conflicting files? That would send them to
>    the bit bucket, wouldn't it? I suppose you'd still
>    be stuck with the directories, but that's probably
>    not that bad.

This is not as bad, but I'm stuck with several hundred files
here. So probably I'm writing a script to deal with them.

Laurynas