Hey Alexander, Your commit has now been merged to the official repos: - official source of truth: https://gitbox.apache.org/repos/asf?p=impala.git;a=commit;h=c925807b1a3eacf1ca3d0e78f6a0fa043b350174 - github.com mirror: https://github.com/apache/impala/commit/c925807b1a3eacf1ca3d0e78f6a0fa043b350174
The long story behind the delay is that when Gerrit reports your commit as "merged", it means only that it has merged the commit to its own internal representation of the "master" branch. This merge can happen automatically, if the patch received a Code Review +2 vote before the precommit tests succeed. ASF's rules mandate that commits may only get merged to an Apache project's git branch(es) via a conscious manual action of the project's committers. For Impala this means that one of the Impala committers has to transfer the merged commits from Gerrit's "master" branch to the official Apache repo at gitbox.apache.org/repos/asf/impala.git This is usually done by invoking bin/push_to_asf.py from the Impala repo and supplying committer credentials when requested. For this to happen a committer actually needs to run the script, which can take some time after the Gerrit merge happens; it rarely takes more than a day in practice. Hope this explains the process, and thanks for your contribution, - LaszloG On Mon, Sep 20, 2021 at 11:27 PM Alexander Saydakov <sayda...@yahooinc.com> wrote: > Hi! > As I understand it, my proposed changes have been merged somewhere. > https://gerrit.cloudera.org/#/c/17818/ > Where should they go? I am looking at the Github repo, and I don't see the > changes there. > Could someone clarify this for me? > Thank you. >
