RE: Git for RPG source code management

So do we just need to make sure that the "local" repository is an IFS file share that the RPG developers are working on, rather than their local C:\ drive?

Or does RDi temporarily push the code up to the IBMi from the users local C:\ drive to get compiled and not require any IFS interaction at all?

-----Original Message-----
From: Mark Murphy [mailto:jmarkmurphy@xxxxxxxxx]
Sent: Wednesday, October 25, 2017 2:10 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Git for RPG source code management

So Git doesn't really have a server right? You have Git installed on the machine that holds your source, and you have your local repository with your source there, and you also may have a remote repository on another machine, or even the same machine if you want. You can have as many remote repositories as you want. A remote repository is just the one that is not your local working copy. You can call any remote repository the central repository if you want, but you can push and pull source between your local and any remote repository. You will, however, need a repository on any machine or directory that you want to maintain a copy of the source. The other major difference is you don't check out a source file. You can checkout a repository which synchronizes your working copy of the source with the local repository. You always have a full copy of your source in your working directory, and as you make changes, you can check those changes in to your local repository. There is a lot more to git, and it does not work like traditional source control systems, so forget about all the terms you know as the ones that sound the same mean different things.


On Wed, Oct 25, 2017 at 2:39 PM, Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx

wrote:

You could mount your source code IFS directory on a machine Git runs on.

On Wed, Oct 25, 2017 at 12:24 PM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:

All,

I've read this over:
http://yips.idevcloud.com/wiki/index.php/PASE/Git

However, it seems to want the Git server running on the IBM i.

We already have a Git Server (VSTS/TFS Online). We don't want
another

one.

What would be the steps to store all our source code on a remote Git
repository so that we can get all the advantages VSTS / TFS provides
you (code reviews, source code check-ins to bug/workitem linking,
sprint planning, global source code searching).

Matt
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you
received this communication in error, please contact the sender and
delete/destroy all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD