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=-4.0 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 3C1C91F4BD for ; Fri, 4 Oct 2019 09:29:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731254AbfJDJ3m (ORCPT ); Fri, 4 Oct 2019 05:29:42 -0400 Received: from mail-wm1-f68.google.com ([209.85.128.68]:34452 "EHLO mail-wm1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726978AbfJDJ3l (ORCPT ); Fri, 4 Oct 2019 05:29:41 -0400 Received: by mail-wm1-f68.google.com with SMTP id y135so9154869wmc.1 for ; Fri, 04 Oct 2019 02:29:39 -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=x5/y/gCkQ70sCMX8PqfnoPRT+s2QW726tph4/n1j4QY=; b=l0k+Ptn+iL/I7zMdPZfE3LZc0tdIdl6mM4DzPD93oZ2vACC+41ZCFLc6deOM3i5sSr H1H4LEo9QPT7dJE/Z0Dh0GxtzvQJMiJZvCd2IEht01sMTqhuxRg8gBrHELfIXcWsXNFp wHd7m3Tlo3yv4updP+FP1DLxMaAbNQRYWD0yMJcALIcLePqZn24W6RXCdJxDcf3aww7R 53CmdAmj+gRypCwWEgdvdJlGlPkKLYITPq2e6f7nSwUkrR+xmFlfljoAVKUf/jf+Fzy8 s4wA699nj328KpYLWMQ0jf1WSiwu5vxY/SnsV6Pl2bTduHfUtrjhCCXyDscf7aoxvxwp NMGw== 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=x5/y/gCkQ70sCMX8PqfnoPRT+s2QW726tph4/n1j4QY=; b=ZfrmUuDHT6W3qpn+/drUnzmb98oX8PRgVs5HPl7emkn7ExnjQ/Zgbsxuzq/7Xsyu3S 7TbH5449yVNxQ9VYYbjhruUuyj8A4vDGE15sZWQ1vaYeI4gNmpOlJq/ZdZdjLCCHA3ur 6B6R7H9NZpLIYP0+KW2erdOkjaxN8hbSxCMNCYOpy7fH0HDOOTTm6ciTqPHe3itc5jHm P53EyOzX92kxCjciyhw2tDNOQQCxBtIC6eUll6nPmhwD2Tz6UJbuc3GQytJJK2qRUJ6J zb0NcyJB0Iy8BnBxIowMFt+PNLbqUxhk6rcnyvT3asMaxvP/vnWnoZRoa70gYjPzA+uT O/UA== X-Gm-Message-State: APjAAAVpg6mqKu/4+ilXgtNYI/8KMiLmem4ViAg42mDPyAOZj/q959WU HLwhPNYp0l7tpT0rmDtNcY3bObNa X-Google-Smtp-Source: APXvYqyW9qw9MSjxEe78BpjLbxLCaOgttbkOrtvF3hrdy8S+cQlyPj5znt40h0GEWnf/fYUdLNmZdg== X-Received: by 2002:a7b:c5c2:: with SMTP id n2mr9822513wmk.20.1570181378736; Fri, 04 Oct 2019 02:29:38 -0700 (PDT) Received: from [192.168.2.240] (host-92-22-28-119.as13285.net. [92.22.28.119]) by smtp.gmail.com with ESMTPSA id a7sm10769167wra.43.2019.10.04.02.29.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 04 Oct 2019 02:29:38 -0700 (PDT) Reply-To: phillip.wood@dunelm.org.uk Subject: Re: [PATCH v4 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> <20190907115034.14933-1-rohit.ashiwal265@gmail.com> <20190907115034.14933-2-rohit.ashiwal265@gmail.com> From: Phillip Wood Message-ID: <9e311cef-1f9d-4146-c2a7-c8179cdcdaf1@gmail.com> Date: Fri, 4 Oct 2019 10:29:36 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <20190907115034.14933-2-rohit.ashiwal265@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Rohit On 07/09/2019 12:50, 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. > + > --whitespace=