Are you sure you want this? The changes we have been working on are to introduce support for the enhanced 5250 protocol and the work is far from complete. While using cvs HEAD in the traditional way (i.e. not using enhanced 5250) doesn't cause any problems, I wouldn't really call the changes "stable". I think it may be best to leave b0-16 alone?

If you're worried about it, make a PREENHANCED tag for both branches. That way, we can always check out the changes from before your code was added if we really need to.


I just think it's much easier to maintain if you commit your changes to both branches before they diverge so far that it'd be a nightmare to bring them back to the same level again.

Plus, having the support in CVS for both branches will reach the most amount of people -- which means you'll get the most amount of testing.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.