On Aug 5, 2021, at 11:32 PM, kekronbekron <000002dee3fcae33-dmarc-requ...@listserv.ua.edu> wrote: > >> I periodically copy over the current libraries and push the changes to >> GitHub. > > Do you mean push to GitHub and then 'build/deploy/copy over the current > (PARMLIB) libraries using some build workflow?
I have a script in my repository that runs commands like “rm sys1.parmlib/*; cp "//'sys1.parmlib'" sys1.parmlib” (where “sys1.parmlib” is a directory in the repository.) After running it I commit the changes and then push to GitHub. > >> It’s not perfect, but I can get some idea of when a change was made or find >> an older version of a member that isn’t working right. > Why is it not perfect, what would you want to work better? “Perfect” would be if git could manage the actual PDS(E)s, but that seems like a lot to ask for. -- Pew, Curtis G curtis....@austin.utexas.edu ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
