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 2D6781F461 for ; Tue, 20 Aug 2019 13:56:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730030AbfHTN4L (ORCPT ); Tue, 20 Aug 2019 09:56:11 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:42290 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728248AbfHTN4K (ORCPT ); Tue, 20 Aug 2019 09:56:10 -0400 Received: by mail-wr1-f68.google.com with SMTP id b16so12511284wrq.9 for ; Tue, 20 Aug 2019 06:56:09 -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=Y0/6sMdpF9s+fqTJN5vbPoX/4XMpmvx5y+wzHU+kbu4=; b=fgl1wkKc58fdPS1eOrQ7mo86szEC/4b+hTsV7RI/t94GRCmoTaACN2+3fyaKXMSY+B Dfp+P9ML+6YRPQv/AcsEpjBU5+nohPj7y6CkFN+NgOvOvqiVtBme5B30GoEI9jJUxZuh TzqRqq19OFTO6LlhxvU99C6NH0jB3yFmuS5BwmtOx4WssQKze8iQzN7dGgwybU12x311 86sKKpBkmrij5pkfY59ZYkh6b4l4wAkpNQvOpGNiTEHTkRpiFwvNjeF1WBmd1jDJ9M7d Ecc9loEJ6SIxKGwpmzPKGFpVhR56VtwjbH3L32pkX9ntYzoW6LsdTH8+4tP8FBlI3ott Jyvw== 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=Y0/6sMdpF9s+fqTJN5vbPoX/4XMpmvx5y+wzHU+kbu4=; b=tXhbqcvKjkQ5jr3996U3C7Bk74cXQ0uafVe0gI7CgVpb90l4yG3csGQvd5UK/ZbLkc 9w8cjJgtSKLxT1nK3RnJnhuVujVRhymBa/UXDjXTnZd00zyHloOOsPP/HTRThdXwPyLQ 1rCON4zwUkxKJtcYE4GeBm58cobEU4yh8aTL8KeRDDUgveVEDv36jPx7I8p0V9xRYPc0 bfRqffUBOgDcvKcteC+or0EMEt89O5EqczLqPYPV7j/i5UdgBM8YDyGKy1yp/9VWUKWq ZjhrzJjxXY3KHcXJgXTiZlXVyKAQbRJ4rDC5RgAEG6aPnA4i1sDe+DAt5lis7XK3+QH6 FjNA== X-Gm-Message-State: APjAAAVw2wIBaGdxsG8hStE3ry8qVchPWrnfXsAjAFSmyyWVcGwOAT0K YbsAgbslBogOtD003mD5tv6tGUDAKGw= X-Google-Smtp-Source: APXvYqxpQ8acVbEsMdrOF6cA5UTlgnOVNCfCYdVd3BQ0CHDjMA0XSnnU9ORIstceabx3YeDXm9h7CQ== X-Received: by 2002:adf:ea08:: with SMTP id q8mr11313724wrm.188.1566309368375; Tue, 20 Aug 2019 06:56:08 -0700 (PDT) Received: from [192.168.2.240] (host-92-22-12-34.as13285.net. [92.22.12.34]) by smtp.gmail.com with ESMTPSA id o11sm54437wmh.46.2019.08.20.06.56.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Aug 2019 06:56:07 -0700 (PDT) Reply-To: phillip.wood@dunelm.org.uk Subject: Re: [PATCH v3 0/6] rebase -i: support more options 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> From: Phillip Wood Message-ID: <71c313d7-e08d-f62f-c52e-aabca0d97002@gmail.com> Date: Tue, 20 Aug 2019 14:56:06 +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-1-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: > I've tries to incorporated all the suggestions. It is helpful if you can list the changes to remind us all what we said. (as a patch author I find composing that is helpful to remind me if there's anything I've forgotten to address) Also there are a couple of things that were discussed such as splitting up the author and passing it round as a tuple and testing a non-default timezone which aren't included - that's fine but it helps if you take a moment to explain why in the cover letter. > > Some points: > - According to v2.0.0's git-am.sh, ignore-date should override > committer-date-is-author-date. Ergo, we are not barfing out > when both flags are provided. > - Should the 'const' qualifier be removed[2]? Since it is leaving > a false impression that author should not be free()'d. The author returned by read_author_ident() is owned by the strbuf that you pass to read_author_ident() which is confusing. Best Wishes Phillip > > [1]: git show v2.0.0:git-am.sh > [2]: https://github.com/git/git/blob/v2.23.0/sequencer.c#L959 > > Rohit Ashiwal (6): > rebase -i: add --ignore-whitespace flag > sequencer: add NULL checks under read_author_script > rebase -i: support --committer-date-is-author-date > sequencer: rename amend_author to author_to_rename > rebase -i: support --ignore-date > rebase: add --reset-author-date > > Documentation/git-rebase.txt | 26 +++-- > builtin/rebase.c | 53 +++++++--- > sequencer.c | 135 ++++++++++++++++++++++-- > sequencer.h | 2 + > t/t3422-rebase-incompatible-options.sh | 2 - > t/t3433-rebase-options-compatibility.sh | 100 ++++++++++++++++++ > 6 files changed, 289 insertions(+), 29 deletions(-) > create mode 100755 t/t3433-rebase-options-compatibility.sh > > Range-diff: > 1: 4cd0aa3084 ! 1: e82ed8cad5 rebase -i: add --ignore-whitespace flag > @@ -19,10 +19,13 @@ > 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. > ++ 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=