From: Don Zickus on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_54517...
@jmflinuxtx @hertonrk-rh - here is the problem as described in issue #35
and #32 and Prarit's MR !588, users are 'forking' the kernel-ark into
the personal space and cloning that. That is their 'origin'. The
reason is, they do not have permission to push directly to 'origin'
(unlike us). They then add an 'upstream' tree that points to cki-
project/kernel-ark. Because 'master' requires that branch to be checked
out and constantly sync'd, it was suggested it was easier to look at the
'upstream/master' branch instead.
Of course this conflicts with how some of use origin/master for the same
affect.
But according to the documentation,
https://cki-
project.gitlab.io/kernel-ark/, we tell people to use 'upstream'.
So my goal is to sync all this up: documentation, 'make dist-*' and
development workflow so everything works as communicated.
I can add 'origin/master' to the list of things to check to if that
helps?
Thoughts?