On Wed, Nov 25, 2020 at 06:10:21AM +0100, Thorsten Leemhuis wrote:
> Lo!
> 
> Am 24.11.20 um 23:22 schrieb GitLab Bridge on behalf of dzickusrh:
> > From: Don Zickus <[email protected]>
> > 
> > The workflow has recently changed such that all development is done
> > on the 'os-build' branch.  Update the docs to show how easy it is
> > to make a change, commit it, generate the srpm and upload it to koji.
> > […]
> 
> While you are dealing with this a quick question: What's the best way to use
> the ark tree to build a vanilla kernel these days? When fedora rawhide
> started to use ark that was easy, because all the patches that actually
> modified the kernel code for real where in a separate, optional branch (that
> was only a few month ago, but forgot the name already, sorry...). But I lost
> track how to do that now everything is mixed up in the os-build branch and
> it's something I'd like to use to build my kernel vanilla packages
> (https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories ) straight from
> ark.

Ok. Fair question. :-)  Folks did not like the separate ark-patches branch,
so I combined it with os-build to make development easier, but created a gap
for vanilla kernels as you described.  Other RHEL folks requested the same
thing to apply the redhat/ infra to various upstream submaintainer trees.

My plan at the time was to auto-create another branch say 'redhat-infra'
(bad name I know) that stripped Red Hat patches out of os-build leaving just
the redhat/ directory on top of upstream 'linus' branch.

Then you could take any upstream branch and just 'git merge redhat-infra' to
quickly add in the RH infrastructure pieces.  And that would address your
concern, I believe.

However, that did slip off my radar and I never finished writing that script
to generate that branch.

But assuming I did finish that script, would the spirit of that approach
work for you?  (aside from a better name [suggestions welcome])

Cheers,
Don
_______________________________________________
kernel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]

Reply via email to