Re: Code cleanup and documenting -- LINUX5250

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: [LINUX5250] Code cleanup and documenting
From: Scott Klement <klemscot@xxxxxxxxxxxx>
Date: Wed, 20 Mar 2002 23:49:22 -0600 (CST)
List-archive: <http://archive.midrange.com/linux5250/>
List-help: <mailto:linux5250-request@midrange.com?subject=help>
List-id: Linux 5250 Development Project <linux5250.midrange.com>
List-post: <mailto:linux5250@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/linux5250>,<mailto:linux5250-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/linux5250>,<mailto:linux5250-request@midrange.com?subject=unsubscribe>

This appears to be the same patch that I applied earlier.   Or am I just
losing my mind?  I'm starting to think that it's the latter :)

Could you verify that everything is correct in CVS?  I'm guessing that I
already applied the "new patch" without knowing it...

On Wed, 20 Mar 2002, James Rich wrote:
>
> You had better apply the new patch I just sent since it contains some
> changes to scs.c that I accidentally left out of the first patch.
>

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Code cleanup and documenting , James Rich

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.