Hi, Alex! Thanks for the response! What would be a proper way to fix this problem then?
Konstantin On Fri, Feb 23, 2024 at 2:24 PM Alexander Kanavin <alex.kana...@gmail.com> wrote: > > It's probably just a simple oversight. If the problematic code path is > not taken in automated tests, no one will see the issue when it's > introduced by the commit. > > Alex > > On Thu, 22 Feb 2024 at 16:11, Konstantin Aladyshev > <aladyshe...@gmail.com> wrote: > > > > Hello! > > I was investigating some problems with the `devtool modify linux` > > command and have discovered that part of the problems is generated > > from the commit > > https://git.yoctoproject.org/yocto-kernel-tools/commit/?id=923a9de418b3ca8592c3fd0a0d0b1e4b29533891 > > This commit is very simple and just adds the `--no-verify` flag to the > > `git am` command. The problem is that this flag was added pretty > > recently (Jan 5 2023 - > > https://github.com/git/git/commit/566902f2db3bdad9be7fb083c713f0d21acf111e) > > and my host git doesn't have it. > > Is it normal that yocto relies on such modern git? Because the yocto > > documentation just says `Git 1.8.3.1 or greater` > > (https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#compatible-linux-distribution). > > And `git am --no-verify` works from something like `v2.31.6` > > apparently. > > > > Best regards, > > Konstantin Aladyshev > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62578): https://lists.yoctoproject.org/g/yocto/message/62578 Mute This Topic: https://lists.yoctoproject.org/mt/104509876/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
