From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yann Droneaud Subject: Re: git merge behavior Date: Fri, 22 Mar 2013 10:16:20 +0100 Organization: OPTEYA Message-ID: References: <1363704914.6289.39.camel@test.quest-ce.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: To: Max Nanasy , Junio C Hamano X-From: git-owner@vger.kernel.org Fri Mar 22 10:16:54 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UIy5l-0004zj-6g for gcvg-git-2@plane.gmane.org; Fri, 22 Mar 2013 10:16:53 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754201Ab3CVJQY convert rfc822-to-quoted-printable (ORCPT ); Fri, 22 Mar 2013 05:16:24 -0400 Received: from mx-out.ocsa-data.net ([194.36.166.37]:60644 "EHLO mx-out.ocsa-data.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753945Ab3CVJQX (ORCPT ); Fri, 22 Mar 2013 05:16:23 -0400 Received: from [192.168.111.12] (helo=rc.ouvaton.coop) by mx-out.ocsa-data.net with esmtpa (Exim - FreeBSD Rulez) id 1UIy5E-000A96-8j; Fri, 22 Mar 2013 10:16:20 +0100 In-Reply-To: X-Sender: ydroneaud@opteya.com User-Agent: Roundcube Webmail/0.8.4 X-abuse-contact: abuse@ocsa-data.net Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Hi, Le 21.03.2013 21:31, Max Nanasy a =C3=A9crit=C2=A0: > Yann Droneaud opteya.com> writes: > >> >> 3) Merge options can't be overridden. >> >> If I modify .git/config to set a merge option, for example forcing >> fast-forward merge, this option cannot be overridden on command=20 >> line: >> > > (git merge --no-ff-only --no-ff) should work. The --no-ff-only=20 > overrides > the --ff-only configuration setting, and the --no-ff ensures that the= =20 > merge > is not a fast-forward. > Thanks. I wasn't aware of the --no-ff-only option and thought --no-ff would be the opposite of --ff-only, or at least disable it given the order of the options. Please find a patch to document option --no-ff-only Documentation/merge-options.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/merge-options.txt b/Documentation/merge-options.txt index 0bcbe0a..20a31cf 100644 --- a/Documentation/merge-options.txt +++ b/Documentation/merge-options.txt @@ -37,6 +37,10 @@ set to `no` at the beginning of them. current `HEAD` is already up-to-date or the merge can be resolved as a fast-forward. +--no-ff-only:: + Disable `--ff-only` behavior, eg. allows creation of merge commit. + This is the default behavior. + --log[=3D]:: --no-log:: In addition to branch names, populate the log message with