Jason Zaman posted on Wed, 12 Aug 2015 15:38:01 +0800 as excerpted: >> Tho I can definitely think of a non-traditional use for bisect. >> [When a system hasn't been updated in over a year, bisect the update.] > > I like the idea, but its probably easier to just git checkout $(git > rev-list -n 1 --before="2015-12-01 12:00" master) and then you just > change the date a month at a time or something
You're correct, and I did think about that, but... The nice thing with bisect at least in something like the kernel where most of the direct main-tree changes are merges, is that it'll stay at the higher merge level as long as possible, drilling down to individual commits only after bisects to an individual merge. Again, however, I'm not entirely sure how that translates to gentoo's rebase-and-fast-forward recommendation, with fewer merges. But at the 3-4 month level, if it avoids landing in the middle of a kde or gnome update, that'd be very useful. It could well be that with gentoo's merges-discouraged workflow, the effect would be the same either way, in which case, you're correct, your suggestion would be easier. But it's still a creative use of bisect I hadn't thought of before, even if bisect isn't the most efficient method to that end. Which means I know a bit more about bisect than I did. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
