From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [PATCH] merge-recursive: handle file mode changes Date: Thu, 13 Mar 2008 17:08:26 -0700 Message-ID: <7vejaew4jp.fsf@gitster.siamese.dyndns.org> References: <20080308171726.GA16129@localhost> <20080313125229.GA24758@localhost> <20080313192246.GA30361@localhost> <20080313224741.GA5000@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Fri Mar 14 01:09:20 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1JZxU7-0003Yr-Ff for gcvg-git-2@gmane.org; Fri, 14 Mar 2008 01:09:19 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755234AbYCNAIj (ORCPT ); Thu, 13 Mar 2008 20:08:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755065AbYCNAIj (ORCPT ); Thu, 13 Mar 2008 20:08:39 -0400 Received: from a-sasl-fastnet.sasl.smtp.pobox.com ([207.106.133.19]:60908 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755564AbYCNAIi (ORCPT ); Thu, 13 Mar 2008 20:08:38 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 81B101BAD; Thu, 13 Mar 2008 20:08:36 -0400 (EDT) Received: from pobox.com (ip68-225-240-77.oc.oc.cox.net [68.225.240.77]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id D9CF61BAB; Thu, 13 Mar 2008 20:08:33 -0400 (EDT) In-Reply-To: <20080313224741.GA5000@localhost> (Clemens Buchacher's message of "Thu, 13 Mar 2008 23:47:41 +0100") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Clemens Buchacher writes: > I am not exactly sure how I should set the result.merge flag. In this context > it seems to have the exact opposite meaning of result.clean. Is that correct? My reading of the code is that result.merge is "if a content level merge has happened", and result.clean is "given that a content level merge has been attempted, was it done cleanly, or are there conflicts for the user to fix in the result". If result.clean is not true, we obviously cannot store the result in stage #0. The result.merge flag is used only for reporting purposes; I am not sure why the non-rename codepath does not pay attention to the result.merge, though.