From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545205029
I think adding origin/master would help. But it always exists, so may be
it's not the behavior you want here, to show an error/force the
developer to setup an upstream remote or
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545178822
@dzickusrh Our documentation has been wrong for a year. Cloning the
project to your own namespace should grab all branches, so origin/master
should still just work. origin/ should point
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545176162
@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
Hi Don,
Don Zickus (via Email Bridge) schreef op ma 05-04-2021 om 21:27 [+]:
> Also ran some bash scripts to find another 60 or so duplicates.
Lazy question (I had trouble skimming the diffs): what actually do you mean
with "duplicates"?
Thanks,
Paul Bolle
From: Don Zickus
Remove duplicate configs acroos fedora, ark and common
Started with a bunch of scripts to filter out duplicates. Then
ran into all the override quirks and quickly and to revert large
chunks of it.
What is left is duplicates and cleanups of a small set of configs.
The SPEAKUP
From: Don Zickus
Combine duplicate configs across ark and fedora into common
Used redhat/configs/evaluate_configs -j and it made these changes.
Signed-off-by: Don Zickus
diff a/redhat/configs/ark/generic/CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND
From: Don Zickus on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/996
Used redhat/configs/evaluate_configs -j and it made these changes.
Also ran some bash scripts to find another 60 or so duplicates.
Signed-off-by: Don Zickus's avatarDon Zickus
From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_544919319
@dzickusrh in line with Justin said, why we care about upstream or
"master" branch here, why not use origin/master since that exists
already for kernel-ark checkout?
There is
From: Augusto Caringi on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/898#note_544914369
request-ack-nack-evaluation
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_544834861
Yes, for the stable branches, we don't care about master. I use
$UPSTREAM as a variable for the git --log, upstream is passed as an
argument for genspec and defined in
10 matches
Mail list logo
