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, 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 A4E7C1F463 for ; Tue, 3 Dec 2019 17:06:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726480AbfLCRGd (ORCPT ); Tue, 3 Dec 2019 12:06:33 -0500 Received: from smtprelay02.ispgateway.de ([80.67.18.14]:54611 "EHLO smtprelay02.ispgateway.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726105AbfLCRGd (ORCPT ); Tue, 3 Dec 2019 12:06:33 -0500 Received: from [24.134.116.61] (helo=[192.168.92.208]) by smtprelay02.ispgateway.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from ) id 1icBd6-0005cv-Kn; Tue, 03 Dec 2019 18:06:28 +0100 Subject: Re: [PATCH v4 00/13] Add --pathspec-from-file option To: Junio C Hamano , Alexandr Miloslavskiy via GitGitGadget Cc: git@vger.kernel.org References: From: Alexandr Miloslavskiy Message-ID: Date: Tue, 3 Dec 2019 18:06:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Df-Sender: YWxleGFuZHIubWlsb3NsYXZza2l5QHN5bnRldm8uY29t Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On 03.12.2019 17:55, Junio C Hamano wrote: >> Changes from V3: > > Yikes, perhaps our mails crossed or something? I think the previous > round is already in 'next'. > > Let's wait and see they cook enough to graduate to 'master', and > build a separate series on top to teach other commands the option > using the facility introduced by the current series (which is the > first 6 patches you sent here). My intent is to support more commands, so I was working on other patches in the background. Today more patches were ready and I wasn't sure whether to submit another topic or continue the old one. After some thinking, I decided to continue the old one. Apparently, I guessed wrong :) Roger: I will wait until the first part graduates to 'master', then submit more patches. Please give me an advice: when the time comes, shall I prepare even more patches and submit a massive branch, or shall I submit today's remaining patches, then wait again? I imagine that massive branches are scary and will deter reviewers?