* [email protected] <[email protected]> [04-28-19 09:50]:
> Andreas Schneider (2019-Apr-28, excerpt):
> > Also you should create a git repo in your pictures directory and
> > check all XMP files into git! So in cases something goes wrong you
> > can go back!
>
> I have stopped doing this. The reason I've started using git for XMPs
> was that DT always writes the XMP files,
there is an option to not write xmp files all the time:
options -> core options -> xmp ->
write sidecar file for each image
> while all other software requires the user to conciously save a file or
> document to make changes permanent. It turned out that DT quite
> frequently took the liberty of changing XMPs without me editing
> something, so git listed a *lot* of unstaged changes. I assume it was
> due to visiting files last visited with older versions of DT. So I was
> faced to isolate my edits from the updates by darktable, which turned
> out to be an impractical mess. Realizing that, I've stopped using git
> for this purpose.
>
> DT's approach to always write to XMPs is something I'm still not
> comfortable with, especially since an edit is just an unconcious touch
> of the scrollwheel away. But I've given up throwing excessive
> complexity (git) at this design choice, and I just hope for the
> best...
>
> I'll do a backup of all XMPs before upgrading darktable.
>
>
> --
> http://stefan-klinger.de o/X
> I prefer receiving plain text messages, not exceeding 32kB. /\/
> \
> ___________________________________________________________________________
> darktable developer mailing list
> to unsubscribe send a mail to [email protected]
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
Registered Linux User #207535 @ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to [email protected]
