2021. What an interesting year. With the world turned upside down by a pandemic that seemingly had its sights set on...
Git release 2.30 now released; built and tested, by ITUGLIB
Randall S. Becker
Hi git fans and users.
Git release 2.30 has now been released by the git development team, and built and tested, by ITUGLIB. As usual, there are builds for J-series and L-series as well as OpenSSL 1.0.2 and 1.1.1.
OpenSSH and NonStop SSH are supported as usual, but you should make sure you are on at least NonStop SSH ADF.
The release has some new features:
- The build settings have changed to be more standard. As NonStop evolves, I typically contribute these changes.
- The new initial branch has changed from master to main. This will not change for existing repositories, but new repositories will get a main branch as the default branch unless you override this. Latest versions of GitHub, BitBucket, and GitLab have also done this. NSGit is also compatible with this change without needing a new version – we knew this was coming a long time ago. This change may impact some scripting you might have done around repository creation and management.
- git diff has been enhanced to exclude parts of files matching regular expressions. This is a cool feature if your files are large and complex.
- Compression is being continually improved to save space in repositories.
- You may have seen some suggestions git provides when you make a typo entering a command, like clown will report that you might have meant clone. You can now configure git to automatically execute the command if the suggestion is unique. This may cause issues for NSGit, because it does not know what you might mean for esoteric git commands. You can control this using the help.autocorrect=never setting in your .gitconfig file. I would suggest putting this setting in anyway because the uniqueness of a typo will change over time and if you have a typo in a script you won’t know it until the command stops being unique and your script will fail at just the wrong moment – like during a production deployment. That would be very bad.
- There have also been a large number of bugs fixed with this release, which makes it useful.
From my point of view, this is comparatively a fairly big release, so while you’re at it, also install OpenSSL 1.1.1. They way you can test both at the same time.
You should, of course, test the release in your environment just to make sure it works for you.
Happy Code Managing!
Randall S. Becker, Managing Director, Nexbridge Inc.,
Process Maintainer and Open-Source Contributor for ITUGLIB.