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, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,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 65A801F619 for ; Wed, 4 Mar 2020 11:52:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387488AbgCDLwM (ORCPT ); Wed, 4 Mar 2020 06:52:12 -0500 Received: from forward501j.mail.yandex.net ([5.45.198.251]:54973 "EHLO forward501j.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726502AbgCDLwM (ORCPT ); Wed, 4 Mar 2020 06:52:12 -0500 Received: from mxback7q.mail.yandex.net (mxback7q.mail.yandex.net [IPv6:2a02:6b8:c0e:41:0:640:cbbf:d618]) by forward501j.mail.yandex.net (Yandex) with ESMTP id 2B0BC3380B7D for ; Wed, 4 Mar 2020 14:52:10 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback7q.mail.yandex.net (mxback/Yandex) with ESMTP id RXDLFTwpNa-q98KwnvL; Wed, 04 Mar 2020 14:52:09 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1583322729; bh=b+bPNBu/Zk0yLzgj8SX3MNz2cR7W1tsvDfLWwhbnofw=; h=References:Date:Message-Id:Subject:In-Reply-To:To:From; b=LMzcXLioIPwg3RcCRdJRea9U1gaSt9kyxHEi3KNRLi9EHD5KVqIL5LeV+DK96xJdb KqAlqU/8qR6HRwCXFVUWv/PzjWvKPHFjSn0ZmYnmTCNB4+sS1FahR/CNGJ3uWvyOI4 uoimKJO6vt54KQxdcL5NjUsInilH3rk0OeVofnNE= Authentication-Results: mxback7q.mail.yandex.net; dkim=pass header.i=@yandex.ru Received: by vla1-b1f71bfb4f06.qloud-c.yandex.net with HTTP; Wed, 04 Mar 2020 14:52:09 +0300 From: Konstantin Tokarev To: "git@vger.kernel.org" In-Reply-To: <1223101582917647@iva6-161d47f95e63.qloud-c.yandex.net> References: <1223101582917647@iva6-161d47f95e63.qloud-c.yandex.net> Subject: Re: `git log --full-diff --follow`: conflicting command line arguments MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Wed, 04 Mar 2020 14:52:09 +0300 Message-Id: <22014821583322729@vla1-b1f71bfb4f06.qloud-c.yandex.net> Content-Transfer-Encoding: 7bit Content-Type: text/plain Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 28.02.2020, 22:20, "Konstantin Tokarev" : > Hello, > > Combination of "--full-diff" and "--follow" in git log arguments causes following error with git 2.25.1: > > fatal: --follow requires exactly one pathspec > > This message is certainly misleading when git log is applied to a single pathspec. Bit it would be > useful to make this combination valid and show full diffs for followed history of particular file > (when -p option is also provided). Any thoughts? Can it be considered a bug? -- Regards, Konstantin