aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Jeff <Jeff@web>2018-02-28 14:43:52 +0000
committerGravatar admin <admin@branchable.com>2018-02-28 14:43:52 +0000
commitf25ec2e1081389bcd95a2b3cb5b79c5ac4f6796c (patch)
tree0ddfff1aa76fda4be4d544b855e3d4fc2e8bd961
parent6ebccb0fd71a73f188ee069e0fef6cf7cdee68ca (diff)
Added a comment
-rw-r--r--doc/forum/Is_there_a_way_to_log_what_changed_in_files_committed__44___similar_to_how_git_normally_works_for_coding_files__63__/comment_2_f093b16307bd369399574fc651569b73._comment10
1 files changed, 10 insertions, 0 deletions
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__/comment_2_f093b16307bd369399574fc651569b73._comment 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__/comment_2_f093b16307bd369399574fc651569b73._comment
new file mode 100644
index 000000000..208146ef1
--- /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__/comment_2_f093b16307bd369399574fc651569b73._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="Jeff"
+ avatar="http://cdn.libravatar.org/avatar/99a3c8987afede93f4e5d3212b43ad5f"
+ subject="comment 2"
+ date="2018-02-28T14:43:52Z"
+ content="""
+Yep, that's what I mean! And would I be able to revert to previous commits like if I were using Github to track code? If it's for large files, does it just make a hidden copy of each version of a file every time I add a new commit?
+
+Thanks!
+"""]]