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 1BCD71F461 for ; Mon, 22 Jul 2019 10:00:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729409AbfGVKAq (ORCPT ); Mon, 22 Jul 2019 06:00:46 -0400 Received: from mail-wm1-f67.google.com ([209.85.128.67]:37656 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726846AbfGVKAp (ORCPT ); Mon, 22 Jul 2019 06:00:45 -0400 Received: by mail-wm1-f67.google.com with SMTP id f17so34657441wme.2 for ; Mon, 22 Jul 2019 03:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=i+WnhAldsypm91WcYtAHZzq1e9O1bzvd/7z7MvUyu48=; b=tlFoyoI6j3WOGiFLcQoTK2gTPtp2nS0R89C4BPqFJDQgUnPJwgPr8DDaj94XxvJzcV YJRL5WvTy5hIVWwDSKQOVwGvaRCVXI+2JqUfrgPNwcs1TxrjNXwEudOmju413fc0GQey zYjKhMoJDL4HCQqADRlv5SM7ysvSgHGXbkYgKG5aNpsFaTa1MN1lpz7fFvKK1k/GxQfd gssK0wdjhluaEe3odD+0yNXMcclOqXeeAcE46flyFS4nharNIeHaaEs50JUesGUjHA6t 0+7fPGig3wMZhzM84yWYC+0z/iFC88LHDkTwsgk1wAexVXIMYuOItBlwzv2gJR/Wcjw2 G0cA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=i+WnhAldsypm91WcYtAHZzq1e9O1bzvd/7z7MvUyu48=; b=ZaHi2ZrKDjeXgo/a7c161WtJ7hTfmUV9U9k53BPw6oV8iKzEvc/bQT+ApYIFLpT+KM 2/XxrPsR6LtZcb1HuTvWqa6FqHtZ7PiQyoVpCeOK6rTLmxWGFG9BrdldWd0ED/I8z8fB GLCtY5wrqFXyEbY4TLLUjXfi+UG9C+GM9njj2x1itJViQnrU8l1Wa2i8aXKYDQDAFm1W 14Y+/oKC26R0x2w+fdM9d1syUEvFqhx68gG2TT3uKQlajjllJCFBfMxKgL0jmCVessPe ckLCYS80q4eWJce67Aeq8UmpPTUINssu3mT1m6mRv7aM9SziUlHVE37ezdPvyHItmml7 2nDA== X-Gm-Message-State: APjAAAV/Xse3e1m+5WMkhzPoXNTauqt7Zc5Xe+z/Zr+bHhIdjMyLftI4 N5qy59gRTc9yMOyJBXqwx7GyIjsJ X-Google-Smtp-Source: APXvYqygHMmtCSdScpQnYkat2Njw4VurgqQd1eRzJDuPv5BPFnAFypC7ALjAlRrv8ZH1od6qLNu2rw== X-Received: by 2002:a1c:9cd1:: with SMTP id f200mr61394504wme.157.1563789643216; Mon, 22 Jul 2019 03:00:43 -0700 (PDT) Received: from [192.168.2.201] (host-89-242-178-164.as13285.net. [89.242.178.164]) by smtp.googlemail.com with ESMTPSA id v4sm35563455wmg.22.2019.07.22.03.00.41 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 22 Jul 2019 03:00:42 -0700 (PDT) Subject: Re: [GSoC][PATCH v2 1/1] rebase -i: add --ignore-whitespace flag To: Rohit Ashiwal Cc: Dscho , Git Mailing List , Junio , Martin , Thomas , Elijah References: <20190712185015.20585-1-rohit.ashiwal265@gmail.com> <20190718185514.20108-1-rohit.ashiwal265@gmail.com> <20190718185514.20108-2-rohit.ashiwal265@gmail.com> From: Phillip Wood Message-ID: <6e61e65e-53c2-eb49-2197-03fe9796ef1f@gmail.com> Date: Mon, 22 Jul 2019 11:00:40 +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: <20190718185514.20108-2-rohit.ashiwal265@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Rohit, It's good to see another patch reducing the differences between the rebase back ends. On 18/07/2019 19:55, 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 | 9 +++- > builtin/rebase.c | 26 ++++++++-- > sequencer.h | 1 + > t/t3422-rebase-incompatible-options.sh | 1 - > t/t3431-rebase-options-compatibility.sh | 66 +++++++++++++++++++++++++ > 5 files changed, 97 insertions(+), 6 deletions(-) > create mode 100755 t/t3431-rebase-options-compatibility.sh > > diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt > index 5e4e927647..eda52ed824 100644 > --- a/Documentation/git-rebase.txt > +++ b/Documentation/git-rebase.txt > @@ -371,8 +371,13 @@ 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:: > + This flag is either passed to the 'git apply' program > + (see linkgit:git-apply[1]), or to 'git merge' program > + (see linkgit:git-merge[1]) as `-Xignore-space-change`, > + depending on which backend is selected by other options. > + > --whitespace=