ATTENTION: darktable master may go unstable.
I'm about to merge a commit in master that could make darktable unstable. This is an extensive change from Edgardoh which adds: - mask history (that is a mask is now part of the history and when changed will not change the same mask in the same module in the history. - the possibility to have custom module order (with drag & drop) - a working color space Both Edgardoh and I have used this of course. We have migrated our whole database and have no issue recently. But those changes touch almost all part of the code. So, you're advised to backup your databases. Note that you won't be able to go back to 2.6.x (except if you revert to the saved databases). The merging is done now to let more people test this, report issues and hopefully fix the remaining issue for 2.8. You'll be warned... Now let's bit the bullet... Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
