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



Edmund,

We'd love to move from SVN to Git...

However, we've got a homegrown utility that transfers from the SVN working
copy on our PC to the i. One thing it does is read the custom SVN
property, MEMBER_DESCRIPTION, for an object and updates the source member
text.

Git doesn't support custom properties that we could find...

How do you deal with text for a source member which then becomes the *PGM
object description text?

Is our only choice to add
ctl-opt text('My program description')
or the CL equivalent to every RPG/CL program?



Thanks!
Charles


On Wed, May 16, 2018 at 3:02 PM, Edmund Reinhardt <
edmund.reinhardt@xxxxxxxxxx> wrote:

FYI
In preparation for COMMON I just produced a step by step guide to using
Git with QSYS members (well at least in how to get set up)
It is available on our RDi wiki.
[1]http://ibm.biz/rdi_git_qsys

Enjoy!

References

Visible links
1. http://ibm.biz/rdi_git_qsys
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.