× 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.



i Buck

Interesting thoughts - of course, we use Turnover, don't have git, source is in source members, I open everything in the Turnover RDI plugin worklist - so my focus is on how to do this with pretty-vanilla-RDi functionality.

And I've never liked IBM i projects!!! :) No need when there's a CMS, IMO.

Cheers
Vern

On 6/20/2017 11:34 AM, Buck Calabro wrote:
On 6/20/2017 11:19 AM, Vernon Hamberg wrote:

We have occasion to make the same changes to source members of the same
name and purpose in different environments.
My mind immediately went to diff, but the diff that I have on my 7.3 box
doesn't understand EBCDIC. As an aside, I don't know where that diff
came from; I'm sure I put it in PASE but when and where from...?

After discarding diff out of hand, I started thinking about Git but I
don't know enough about Git to be able to force changes from X onto file
Y. Not yet, anyway.

The way I use Git is on IBM i Projects. The idea being that the PC
directory that holds the project files is just another Git repo. But I
can put a Git repo over ../RemoteSystemsTempFiles if I wanted to... hey!
Maybe I can use Winmerge there too!

The issue with that is that the source sequence and date are in there,
so Winmerge finds a lot of deltas that... aren't. :-(

I think that if I were faced with this problem I'd make some IBM i
Projects and use WinMerge and Push Changed back to the appropriate
libraries.



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-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.