Bug 127039 - Digikam needs to integrate a revision control system
Summary: Digikam needs to integrate a revision control system
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Versioning (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-09 20:34 UTC by Joe Kowalski
Modified: 2022-02-02 05:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 6.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Kowalski 2006-05-09 20:34:12 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          n/a 
OS:                Linux

It would be nice if Digikam could integrate with a revision control system that could handle file level branching so that there would be no need to worry about accidentally overwriting originals (granted this can be done manually, but it requires an extra step to make a backup) and help keep track of which photos are derivatives of the originals.  This feature could make digikam more of a "workflow" oriented app for digital photographers.
Comment 1 Julien Narboux 2006-09-05 18:51:09 UTC
I think this wish could make sense if the "actions list is implemented" : a picture would be the actual picture and a list of actions such as change saturation, crop... as it would be very small this list could be saved using a version managment system.
See comment 6 on bug http://bugs.kde.org/show_bug.cgi?id=125387
Comment 2 caulier.gilles 2006-09-05 20:58:19 UTC
Absolutly Julien. I tag this file like dupplicate. No need to multiply entries with a same subject. It's already difficult to manage B.K.O with a lots of reports.

Joe, please continue to comments in #125387. Thanks in advance

Gilles Caulier

*** This bug has been marked as a duplicate of 125387 ***
Comment 3 caulier.gilles 2019-08-13 20:52:25 UTC
Fixed with bug #125387