From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 73EBD1F461 for ; Tue, 20 Aug 2019 18:41:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729833AbfHTSk7 (ORCPT ); Tue, 20 Aug 2019 14:40:59 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:39099 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728682AbfHTSk7 (ORCPT ); Tue, 20 Aug 2019 14:40:59 -0400 Received: by mail-wr1-f68.google.com with SMTP id t16so13426165wra.6 for ; Tue, 20 Aug 2019 11:40:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=reply-to:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=26XcdZQsAvMJiFSXLFQOqbFqJDMlZiDJ8Ggtw90jD44=; b=Pd29m5g+1LbGgNroV/ju1D6w0+KcfDrVnPu5nD/L7vQJU2XVgUjq2ssaiqd2HpjuU7 +wwzQnheBfjbbGIJEK48IsWd5rc2aSXCIZbHvzVjaPgXCwCFaqvdY7OLoYOsGgXPsxnE TDvEJGZ4sI8bpDBANdP1ILX5UEq5G2OM90t9r0Mm7P1ri0ojTQXuorprQH8lA4k+b786 jrkKnyBxhygbgxR0ck1GmKCoZPtMHGSMF/5OTy6scRTI4By/CM0kD+i5LEmRMRbbmtVW fXmkdztYqxpEcYM78OTs4OHUFxPkeLvI8Usoiqjt1aMjbvLgv28EhQnnWZzWO0RK782B ncjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:to:cc:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=26XcdZQsAvMJiFSXLFQOqbFqJDMlZiDJ8Ggtw90jD44=; b=Ec6bH39CSvMArkuRzQkBvhJFHA/vHgOl4a+U96pUyKRH5SwlH+DvQE4deC0qXaQO7K ReZQtC82EIzPahMKUt8/b5FNUkKp5pFlpLxpJBe5USMzcUaRIbwy0qOVE6jM7XTgV723 GBmrW9V03GKgcVs/EnJlE8Rk8JJzT6GXWXAsi8i5ArIlbyhzx8cx1NNdd3jCBGiRonJW H15u00KfZKqbi0+bC99Od8xQkGdxJAjf7oQworOwUDCb0IGe71swI+juJfIDiQZud4bl Cj94+4FBfZEZW27+sOtngDbr07Hll0ppEt64azJt3bDmy7JxtBdsypnJFTPAwxQw/+vB SvJQ== X-Gm-Message-State: APjAAAUvLTW0OcoEjX7KnHoXZr6h8Rqke+My57S1EBKsmls4TfyoGU4r S61ZGMtL6xuQEVTkZ0bKEEE= X-Google-Smtp-Source: APXvYqxeG56CXRu0bGuu5z1IGn7czOMGDPIdQgWJvJVELyB3w1kIHSOPXt+8Qx+UIErHgEXGVLogRQ== X-Received: by 2002:a5d:66d0:: with SMTP id k16mr22599530wrw.333.1566326456378; Tue, 20 Aug 2019 11:40:56 -0700 (PDT) Received: from [192.168.2.240] (host-92-22-13-95.as13285.net. [92.22.13.95]) by smtp.gmail.com with ESMTPSA id e9sm19236038wrt.69.2019.08.20.11.40.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Aug 2019 11:40:55 -0700 (PDT) Reply-To: phillip.wood@dunelm.org.uk Subject: Re: [PATCH v3 1/6] rebase -i: add --ignore-whitespace flag To: Rohit Ashiwal Cc: Johannes.Schindelin@gmx.de, git@vger.kernel.org, gitster@pobox.com, martin.agren@gmail.com, newren@gmail.com, t.gummerer@gmail.com References: <20190806173638.17510-1-rohit.ashiwal265@gmail.com> <20190820034536.13071-1-rohit.ashiwal265@gmail.com> <20190820034536.13071-2-rohit.ashiwal265@gmail.com> From: Phillip Wood Message-ID: <98aeebc5-fceb-1ce8-9c27-d425c3f6e674@gmail.com> Date: Tue, 20 Aug 2019 19:40:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190820034536.13071-2-rohit.ashiwal265@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB-large Content-Transfer-Encoding: 7bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Rohit On 20/08/2019 04:45, Rohit Ashiwal wrote: > There are two backends available for rebasing, viz, the am and the > interactive. Naturally, there shall be some features that are > implemented in one but not in the other. One such flag is > --ignore-whitespace which indicates merge mechanism to treat lines > with only whitespace changes as unchanged. Wire the interactive > rebase to also understand the --ignore-whitespace flag by > translating it to -Xignore-space-change. > > Signed-off-by: Rohit Ashiwal > --- > Documentation/git-rebase.txt | 13 ++++- > builtin/rebase.c | 22 +++++++-- > t/t3422-rebase-incompatible-options.sh | 1 - > t/t3433-rebase-options-compatibility.sh | 65 +++++++++++++++++++++++++ > 4 files changed, 94 insertions(+), 7 deletions(-) > create mode 100755 t/t3433-rebase-options-compatibility.sh > > diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt > index 6156609cf7..873eb5768c 100644 > --- a/Documentation/git-rebase.txt > +++ b/Documentation/git-rebase.txt > @@ -371,8 +371,16 @@ If either or --root is given on the command line, then the > default is `--no-fork-point`, otherwise the default is `--fork-point`. > > --ignore-whitespace:: > + Behaves differently depending on which backend is selected. > ++ > +'am' backend: When applying a patch, ignore changes in whitespace in > +context lines if necessary. > ++ > +'interactive' backend: Treat lines with only whitespace changes as > +unchanged for the sake of a three-way merge. > + Thanks for spelling out exactly what this does. I had not appreciated the difference before. Does this mean that if I have a branch with some whitespace cleanups I'll get different results if I rebase it with the sequencer compared to am? (I suspect from the description that the sequencer will simply ignore all my whitespace changes) I think this is ready if we can live with the difference - I'm not entirely convinced that adding an option with the same name and a different behavior is going to improve things though. Best Wishes Phillip > --whitespace=