[Dnsmasq-discuss] Whitelist again, git bisect

[Geert Stappers]

On Mon, Apr 11, 2022 at 12:45:38PM +0200, William Edwards wrote:
> Kovács József via Dnsmasq-discuss schreef op 2022-04-11 13:28:
> > 
> > I downgraded the dnsmasq from 2.86 to 2.80 and whitelist is working.
> > 
> > What could be the difference, if the configuration files are same?
> > 
       ...
> > 
> > Could somebody help me?
> 
> You could help yourself by binary searching for the commit that caused the
> change in behaviour ;)
 
Use `git bisect` for it.  Here a snippet from `man git bisect`

   Basic bisect commands: start, bad, good
       As an example, suppose you are trying to find the commit that
       broke a feature that was known to work in version v2.6.13-rc2 of
       your project. You start a bisect session as follows:

           $ git bisect start
           $ git bisect bad                 # Current version is bad
           $ git bisect good v2.6.13-rc2    # v2.6.13-rc2 is known to be good

       Once you have specified at least one bad and one good commit, git
       bisect selects a commit in the middle of that range of history,
       checks it out, and outputs something similar to the following:

           Bisecting: 675 revisions left to test after this (roughly 10 steps)

       You should now compile the checked-out version and test it. If
       that version works correctly, type

           $ git bisect good

       If that version is broken, type

           $ git bisect bad



> > Thank you very much, in advance!

Yes, we are looking forward  you reporting back.



Groeten
Geert Stappers

P.S.
@József your system clock is some hours ahead, please adjust it.
-- 
Silence is hard to parse