On Tue, Oct 27, 2020 at 08:54:37PM +0900, Koichi Murase wrote: > > I tried to bisect but I'm not sure the result is useful. I got the > > following: > > > > d233b485e83c3a784b803fb894280773f16f2deb is the first bad commit > > commit d233b485e83c3a784b803fb894280773f16f2deb > > Author: Chet Ramey <chet.ra...@case.edu> > > Date: Mon Jan 7 09:27:52 2019 -0500 > > > > bash-5.0 distribution sources and documentation > > FWIW, on which branch did you performed bisect? The above commit is > from the branch of distribution. You can perform bisect against > `devel' branch, for example, between 118fb670..5cc55f2f. > > The Bash source is not really managed by the version control system in > a usual sense, but the repository is just a sequence of snapshots. So, > you can only narrow down to a snapshot of some day, but it will become > easier to identify the corresponding changesets.
Thank you for the explanation, Koichi. I thought I had bisected on devel but perhaps I did something wrong. I can attempt another bisect at some point in the future, but these days it is very difficult for me to find time. Thanks for your quick reply! Scott
