Hi Chris, On Fri, Jul 10, 2009 at 12:44 PM, Christoph Steinbeck<[email protected]> wrote: > Not sure why this happened and who did it but that should be easy to > find out.
'git bisect' is your friend... > In principle, I think that Fingerprints can easily change from release > to release (improvements, fixes), but of course that needs to be > clearly stated in the release notes and/or announced on the mailing > lists, so that everyone can regenerate the relevant fingerprints. The problem is, however, that the Fingerprinter has dependencies... and if those dependencies get fixed, it is far from clear that fingerprints change... To discover those, we have a few unit tests, which test that fingerprints do not change... I so I thought... but clearly they failed. Egon -- Post-doc @ Uppsala University http://chem-bla-ics.blogspot.com/ ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Cdk-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdk-user
