The user must have deleted the account.
It is a valid user, as they contacted me privately. I'm looking into what happened. Initially it seems like the post was stuck in approval, as the blog author hadn't checked the comments in a while. But still working on the details.
To me it is pretty normal to have users who do not want to share any details anywhere. Apparently this user did not want to leave a nickname here. That happens, and it's ok.
Of course with the forum there is a problem in deleting nicknames, as Qt Account remembers them and when the user wants to rejoin here, they will get the same nickname (not exactly sure what will happen to orphan posts like this if that happens.). So choosing a nickname is important.
The other take-away here is that people really need to have a channel where they can voice problems when they see them, and someone who takes the issue further. If blog comment approval looks wrong, then it is important to raise it here or in feedback.
it's a two year old thread :)
the -j option in make is used to set how many processes will be used for compiling. It doesn't matter if it's 32 or 64 bit, it's all about the number of cores your machine has. You want them all busy with the compilation, and not idling.
For me it would look like "make -j4" as I'm typing on a heavy desktop machine with four cores (my resource manager shows 8, but that is just Intel hyperthreading showing virtual cores).
Since those are the same patches you should only target one branch. If it's the wrong one, don't worry it will be changed for you.
In order to get them move forward, you should add reviewers that are concerned by your patches e.g. the module maintainers.
One probable remark you will have is that your patch modifies several unrelated stuff so you should split them in order to ensure atomic changes e.g. one disables the item view part, another one the shortcut etc.