On Sun, Nov 19, 2017 at 08:00:35AM -0800, T. Modes wrote:
> There were alone 8 releases of GTK in the last 2 months. So it is difficult
> to find a hint. In 3.22.25 the changelog mentions
If you can use GIT, it is easy to pinpoint the exact commit that
caused the problem. Just tell GIT: This version works,... this one
does not. and then it will suggest a version for you to compile and
test. Once that is done you say: this one works too. Or this one is
bad too. and a new version is provided to test. In a few iterations
you'll have the exact version that introduced the bug.
A condition for this to work quickly however is that you can compile
and test the issue for yourself.
Roger.
--
+-- Rogier Wolff -- www.harddisk-recovery.nl -- 0800 220 20 20 --
- Datarecovery Services Nederland B.V. Delft. KVK: 30160549 -
| Files foetsie, bestanden kwijt, alle data weg?!
| Blijf kalm en neem contact op met Harddisk-recovery.nl!
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/20171120111932.GG6226%40BitWizard.nl.
For more options, visit https://groups.google.com/d/optout.
