Hi Salman, On Mo, 29 Jul 2024, Salman Halim wrote:
> On Mon, Jul 29, 2024 at 8:54 PM Salman Halim <salmanha...@gmail.com> > wrote: > Sorry for the delayed response; I was hoping that the patches were > in individual branches in git so I could just use 'git bisect' to > figure out which patch introduced it. From what I can see, > however, there is only the master branch ('git branch -a'). > > Would you be able to please tell me how I might go back to a > previous patch version? I'm willing to do a manual binary search. I don't see what would be the benefit of having individual patches on individual benefits. It's true, we only use a linear history with a single branch master. You can easily checkout individual patches using tags, e.g. git checkout v9.1.0591 Then you can use git bisect with those tags, e.g. git checkout master && git bisect bad && git checkout v9.1.0500 && git bisect good and then follow gits advise to checkout individual commits, build vim and verify the good or bad behaviour. > I just grabbed Vim 9.1 patch 643 and it seems to be working again. > Somewhere between patch 608 and 643, it got addressed, possibly as a > side effect, possibly because you figured it out. Either way, it's > working now. The issue was also recently reported at https://github.com/vim/vim/issues/15370 and fixed by https://github.com/vim/vim/releases/tag/v9.1.0634 Thanks, Christian -- NEVER swerve to hit a lawyer riding a bicycle -- it might be your bicycle. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ZqiGei/YFmXZDSBo%40256bit.org.