I'm a bit confused about the instructions for upgrading Git from 2.14 to 2.26.
There are some notes:
Once you change a repository with Git for z/OS 2.26.2, this repository won't be compatible with previous versions of Git for z/OS. It is vital that entire team will move to the new version of Gitand
When you clone the repository with Git for z/OS 2.26.2, you need to run git status command. You might see that Git marks some files with the attribute as modified, even if you didn't modify them. ...We recommend to update the files in the index (commands: git add <filename>; git commit).</filename>
Typically different people will be working with separate clones of the repository and different branches, so at what point does the incompatibility occur?
Presumably you can still clone a repository and check out old commits with the old version?
Does the commit for files that 2.26 marked as modified interfere with merging branches, either on z/OS or via pull request?
What happens with e.g. git bisect?
I'm not sure what
"It is vital that entire team will move to the new version of Git" actually means in practice. I fear that it means all branches need to be converted to the new version. Or worse, perhaps branches crossing the release can't be easily merged, so all existing branches need to be merged first.
Can you clarify, and hopefully set my mind at ease?
------------------------------
Andrew Rowley
Black Hill Software
------------------------------