From d901d34e04c9f5930834c8a2e84d66bf6819f67b Mon Sep 17 00:00:00 2001 From: "jeff@184d5cbb24509ab635773e72bc758c99847e45da" Date: Mon, 26 Feb 2018 21:40:11 +0000 Subject: --- ...ilar_to_how_git_normally_works_for_coding_files__63__.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/Is_there_a_way_to_log_what_changed_in_files_committed__44___similar_to_how_git_normally_works_for_coding_files__63__.mdwn diff --git a/doc/forum/Is_there_a_way_to_log_what_changed_in_files_committed__44___similar_to_how_git_normally_works_for_coding_files__63__.mdwn b/doc/forum/Is_there_a_way_to_log_what_changed_in_files_committed__44___similar_to_how_git_normally_works_for_coding_files__63__.mdwn new file mode 100644 index 000000000..5844e7cf4 --- /dev/null +++ b/doc/forum/Is_there_a_way_to_log_what_changed_in_files_committed__44___similar_to_how_git_normally_works_for_coding_files__63__.mdwn @@ -0,0 +1,11 @@ +Hello all, + +I work for a company that produces books using InDesign and marketing assets for these books in Photoshop/Illustrator. + +What we're ultimately looking for is a system that allows us to make changes (primarily to the books) and log the changes to the file so we can keep track of what has been edited when. + +Ideally, we'd also be able to pull up an older version of the file if needed. So if we have 10 commits and are on commit #10, we could pull up commit #7 if needed and see that file as it was back when it was committed the 7th time. + +I hope I explained what I'm looking for clearly. Is this something git-annex could help wtih? + +Thanks -- cgit v1.2.3