Date: Thu, 7 Jul 2022 11:24:47 -0400 From: Ryan Stone <rysto32@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: buildkernel is broken Message-ID: <CAFMmRNyCDzMAcR6dfUAo53399YyaB%2B70ME20oBnOdLAqT-SBEQ@mail.gmail.com> In-Reply-To: <Ysbyl28nKKlr5Kr2@troutmask.apl.washington.edu> References: <YsZptHF8tSttpTVy@troutmask.apl.washington.edu> <CAFMmRNz_FjszHNx92vbV9wezBHwT222w2PKO9WwN1zpWciRo5A@mail.gmail.com> <YsbtBZwfBMmltllg@troutmask.apl.washington.edu> <CAFMmRNyWYGD1UoyqMvTnyCnytKFrH9rPcM01Q2YMxhOQkWNd=A@mail.gmail.com> <Ysbyl28nKKlr5Kr2@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
You could "git cherry-pick -n 37f604b49d4a; git restore --unstaged sys/net/vnet.h" to apply the fix to your local tree without committing it or leaving it staged for commit. On Thu, Jul 7, 2022 at 10:50 AM Steve Kargl <sgk@troutmask.apl.washington.edu> wrote: > > On Thu, Jul 07, 2022 at 10:38:43AM -0400, Ryan Stone wrote: > > Okay, update your tree and it should be fixed then. > > Is it possible to pull just that fix? I spent part of > yesterday building world, and contrary to popular belief, > not all hardware contain a 32-core uber-fast ryzen cpu. > > Can people please test their simple changes prior to > committing? > > -- > Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNyCDzMAcR6dfUAo53399YyaB%2B70ME20oBnOdLAqT-SBEQ>