From 5ecb4944a637c4f28a15746b2ea716850e63a5ab Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 8 Dec 2015 11:55:19 -0400 Subject: comment --- .../comment_3_bdf54ac096c994c33d661b454d89c770._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/Fail_to_push_changes_when_merging/comment_3_bdf54ac096c994c33d661b454d89c770._comment (limited to 'doc') diff --git a/doc/forum/Fail_to_push_changes_when_merging/comment_3_bdf54ac096c994c33d661b454d89c770._comment b/doc/forum/Fail_to_push_changes_when_merging/comment_3_bdf54ac096c994c33d661b454d89c770._comment new file mode 100644 index 00000000..a59296a0 --- /dev/null +++ b/doc/forum/Fail_to_push_changes_when_merging/comment_3_bdf54ac096c994c33d661b454d89c770._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-12-08T15:53:27Z" + content=""" +Looks like a lacking FQDN indeed. There's a property to fix that! ;) + +Git is also picky about the user having a name. + +AFAIK, git does not make commits for fast-forward merges, but it does for +non-fast-forward merges. I suspect that it's making such a merge in your +case. +"""]] -- cgit v1.2.3