From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_546096447
I'm ok keeping the upstream remote for now (short term solution). We can
think more and do further changes if we find a better way to handle it.
__
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_546051611
When you create a fork on gitlab, it should automatically keep it in
sync with the project that you sync from, which means origin/master
doesn't really go out of date any more than os-bu
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545998171
@hertonrk-rh - see my above answer to @jmflinuxtx. I have pondered
on/off the last few months about how to eliminate the whole 'merge-base'
selection as I don't like it and requires git hi
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545993958
@jmflinuxtx - yeah I am trying to address the documentation with !772
and @hadess1 had some questions about the workflow with regards to an
origin tree and an upstream tree. So that MR's c
From: Prarit Bhargava on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/588#note_545955411
Yup, sounds good to me.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedorap
On Mon, Apr 05, 2021 at 11:35:13PM +0200, Paul Bolle wrote:
> 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
>
