summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar DavidEdmondson <DavidEdmondson@web>2011-09-05 15:43:26 +0000
committerGravatar admin <admin@branchable.com>2011-09-05 15:43:26 +0000
commitc5c525d930480ccbf230420efb3b07cfd3ea78d7 (patch)
tree76f476b37a0123d6f7ed56c0edd39d6405df5470
parentea621d0c2d418c6dfe247b0aa3f78976c002b2b2 (diff)
Added a comment: Is it necessary to commit after the 'drop'?
-rw-r--r--doc/walkthrough/removing_files/comment_1_cb65e7c510b75be1c51f655b058667c6._comment8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/walkthrough/removing_files/comment_1_cb65e7c510b75be1c51f655b058667c6._comment b/doc/walkthrough/removing_files/comment_1_cb65e7c510b75be1c51f655b058667c6._comment
new file mode 100644
index 000000000..1c8719cec
--- /dev/null
+++ b/doc/walkthrough/removing_files/comment_1_cb65e7c510b75be1c51f655b058667c6._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="DavidEdmondson"
+ subject="Is it necessary to commit after the 'drop'?"
+ date="2011-09-05T15:43:25Z"
+ content="""
+In fact is it possible? Nothing changed as far as git is concerned.
+
+"""]]