Hi Konstantin, On 17:26-20230919, Konstantin Ryabitsev wrote: > September 19, 2023 at 7:20 AM, "Manorit Chawdhry" <m-chawd...@ti.com> wrote: > > Am not sure either.. I had been using b4 for all the patches and I still > > see that my next revision queued by b4 also has the same problem. Not > > exactly sure what went wrong with b4 but would be careful next time. > > Thanks for pointing it out. > > I'm curious how this happened as well. > Can you please send me the output of: > > b4 prep --version > b4 prep --show-info (while in the branch that caused this problem) >
I believe it had been my mistake, there is a bug in b4 that I had been trying to fix locally but forgot to cover all the cases for that. I believe that caused it to break. The bug is basically that when you apply patch prefix, the prefix actually wasn't behaving like a prefix [0]. I have re-spinned my local fix but if possible, please let me know if there are any mistakes that you see in the current patch as well [1]. If possible, I would like to upstream the fix as well as am not sure where I can reach out to for this. Thanks for reaching out. [0]: https://github.com/mricon/b4/issues/3 [1]: https://github.com/manorit2001/b4/commit/463b32ab67696daec743ba7d85e8dc4da4edb2f1 Regards, Manorit > -K