|
Could you guys please send along the IBM i change control software you’re<mailto:tim.bronski@xxxxxxxxx%0b>> <mailto:tim.bronski@xxxxxxxxx>>
using?
Thank you!
Respectfully,
Michael Mayer
IBM i on Power System Admin
ERMCO-ECI
2225 Industrial Rd
Dyersburg, Tennessee 38024
Office and OnCall: 731.676.4318
Cell: 518.641.8906
Email: michael.mayer@xxxxxxxxxxxxx<mailto:michael.mayer@xxxxxxxxxxxxx<mailto:michael.mayer@xxxxxxxxxxxxx%3cmailto:michael.mayer@xxxxxxxxxxxxx>>
https://www.ermco-eci.com<https://www.ermco-eci.com><https://www.ermco-eci.com/<https://www.ermco-eci.com/>>
IBM i Personal Blog: https://ibmireference.blogspot.com<https://ibmireference.blogspot.com><
https://ibmireference.blogspot.com/<https://ibmireference.blogspot.com/>>
[cid:image001.gif@01D95323.B9E93710]
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of Tim
Bronski
Sent: Friday, March 10, 2023 5:45 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: Re: Rdi - update workspace with more recent source from remote
Thanks Jack,
I did have a look at the iForGit. The issue I have is (probably) a one
time thing. Most of the source code is in IFS but in this case I
inherited an older RDi workspace that has this project in it. I think
it's a little out of date and out of sync with the source on the IBMi. I
could just recreate the project using the IBMi source but I was hoping
RDi had a better way to load or import a source member individually.
On 3/10/2023 2:42 AM, Jack Woehr via MIDRANGE-L wrote:
If it's in the IFS you can revision control the whole project.origin
You can also mount the IFS directories on your local disk using SSHFS and
operate revision control in that fashion.
And you can use iForGit for the OFS portions and separately check in the
project data from your RDi workspace in another dir and use the same
repository as the main repo.Source
There's all sorts of way to do this.
Rule 1: Forget the classic inflexibility of IBM i development. Open
has opened up our legacy box.wrote:
On Thu, Mar 9, 2023 at 6:17 PM Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx%3cmailto:midrange-l@xxxxxxxxxxxxxxxxxx>>>
revision control on
Hey Jack!! I wonder if I see a bit of a challenge here. Tim said he is
using an RDi project - the challenge might be integrating that with git.
Richard talks about his iForGit can work with RDi, but with projects?
Just askin'!!
Cheers
Vern
On 3/9/2023 10:57 AM, Jack Woehr via MIDRANGE-L wrote:
This is called "revision control" and that's what Git is for.iForGit
- If you move to working in the IFS, it's a no-brainer.
- If you want to stay in source physical files in the OFS, then
<https://www.iforgit.com/<https://www.iforgit.com><https://www.iforgit.com<https://www.iforgit.com>>> can offer you Git
those
objects.
On Thu, Mar 9, 2023 at 8:50 AM Tim Bronski <tim.bronski@xxxxxxxxx
----wrote:
I've got a source file on the IBMi with some source members that have
been edited separately, and more recently, than the copy I have in a
project in rdi. Is there an automated way to update the local source
file in a project from the remote copy, if the remote has a newer
timestamp?
Need sFTP or PGP? Download your native sFTP or OpenPGP solutions here:
www.arpeggiosoftware.com<http://www.arpeggiosoftware.com><http://www.arpeggiosoftware.com<http://www.arpeggiosoftware.com>>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx%3cmailto>:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l><
https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx%3cmailto>:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l><
https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto<mailto:support@xxxxxxxxxxxxxxxxxxxx%3cmailto>:
support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx>> for any subscription related questions.
The information in this email may be confidential. It is intended only for
the person(s) named above. If you are not the intended recipient, please
notify the sender and do not review, distribute, or duplicate this email.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
