> On Mar 7, 2015, at 12:16, Peter Dyballa <peter_dyba...@web.de> wrote: > > > Am 16.02.2015 um 18:49 schrieb Jeremy Huddleston Sequoia: > >> Please install 1.16.99.1_3 and tell me if it has the problem you are seeing. > > Hello Jeremy! > > First result: 1.16.99.1₃ already shows the faulty colours and lets GNU Emacs > 24.3 and gkrellm crash. > > Maybe I can start next try in 1.16.99.901_0 20 hours!
No need for that. You said 1.16.99.1_2 doesn't have the issue and 1.16.99.1_3 does, so it was introduced somewhere between 1.16.99.1_2 and 1.16.99.1_3. That means it was something between: git commits cff12936275db2f71f6d24f9ea0985a0d14af454 and e572bcc7f4236b7e0f23ab762f225b3bce37db59 If you are not comfortable building from a git checkout, I suggest you stay at the 1.16.99.1_3 checkout and bisect between those to git commits by editing the git.branch line of the Portfile to figure out what commit introduced the issue. You can do something like: git clone ssh://git.freedesktop.org/git/xorg/xserver.git cd xserver git bisect start git bisect bad e572bcc7f4236b7e0f23ab762f225b3bce37db59 git bisect good cff12936275db2f71f6d24f9ea0985a0d14af454 It will then report something like this: Bisecting: 169 revisions left to test after this (roughly 8 steps) [35dc7c75150733dbcef8a18b6796f49a7c48ebee] Merge branch 'modesetting-import' into master So try 35dc7c75150733dbcef8a18b6796f49a7c48ebee and then run 'git bisect good' or 'git bisect bad' as appropriate and try the next one until you've determined what commit introduced the problem. --Jeremy > -- > Greetings > > Pete > > I consider religion godesque. > > > > > _______________________________________________ > Xquartz-dev mailing list > Xquartz-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/xquartz-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/xquartz-dev
