Restoring the master branch about inifile-cpp HOT 2 CLOSED

Hi @kamchatka-volcano,

first of all thanks for using inifile-cpp and sorry for the inconvenience.
You are right, I just renamed the default branch to main last week and did not expect it to have such an impact on downstream projects.
I re-added a master branch which points to the current HEAD of main. However, I won't be able to move this master branch alongside the main branch, so it will become outdated sooner or later. If you want to keep using the latest inifile-cpp version in your downstream projects, I suggest that you update your references to point to main instead of master, though that's up to you.
Again sorry for the trouble and thanks for reporting.

If the problem has been resolved for you, feel free to close this issue.

from inifile-cpp.

Thank you!

I won't be able to move this master branch alongside the main branch, so it will become outdated sooner or later

It's fine, it fixes all previous releases, which is the most important part.

Again sorry for the trouble and thanks for reporting.

Oh, nevermind, I think it's just a mistake to download dependencies by the branch name. The same issue would happen if you willingly or unwillingly introduced incompatible changes that would break my previous releases. Actually, for me, there's now a positive side that you agreed to create a branch purely for compatibility and it won't be updated later.

That said, have you thought about using version tags? Right now there are none, and I'm thinking of forking inifile-cpp to be able to control its version from the libraries that download it. If you would create one, I could just continue using your original repo.

from inifile-cpp.