dmik
commented
6 years ago Version 5.5.1 and 5.11.0 are imported for both the parent repo and qtbase submodule an OS/2 version of which is hosted here https://github.com/bitwiseworks/qtbase-os2.
BTW, I've found a nice way of importing new tags right from Qt git repositories bypassing the export (via the archive command) that creates an intermediate ZIP. The obvious benefit here is that there is no information loss — every git action is replayed against our repositories. This includes recording commits for submodules and also ignoring git attributes like git-ignore that would make some files (e.g. README.git) gone missing from the exported archive. I will publish a detailed instruction on the wiki page here. It may be reused in other projects that have git-based upstream repositories.
This where everything starts. We will follow the original Qt repository layout where the source code is broken into submodules (see the roadmap for more details) and the parent (this) repository just gather them all and provides some scripts for bootstrapping and similar tasks. This approach will also let us use original repositories as submodules where appropriate (i.e. where no change to the original source code is necessary).
Note that due to the fact that the Qt code base contains lots of commits, it's not feasible to import the full project history from upstream. It will bloat our history too much and drag focus off of the OS/2 development quite a bit. We will use a technique of squashing all original history into a single commit representing a single official release we are about to move to.
So, for the initial import, there will be two distinct commits — one for Qt version 5.5.1 and the other one for Qt version 5.11.0. 5.5.1 is the latest version where QtWebKit is still officially present and we keep it as a distinct point in our history in case if we will ever need to fork an OS/2 version off it. 5.11.0 is the current latest version. This is the one we will start porting now.