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-Status: No, score=-3.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id B1FD21F4B4 for ; Wed, 9 Dec 2020 03:25:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727246AbgLIDXT (ORCPT ); Tue, 8 Dec 2020 22:23:19 -0500 Received: from pb-smtp20.pobox.com ([173.228.157.52]:63070 "EHLO pb-smtp20.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725789AbgLIDXS (ORCPT ); Tue, 8 Dec 2020 22:23:18 -0500 Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 2DDCDFA01C; Tue, 8 Dec 2020 22:22:36 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=qMg/M+kZz5Nfa/uqhZ5UYhu3YYM=; b=ntq0zg Gb4e+Rxt0kG76V4yFHAZmn8WS/dwxzDCajTftNZQvt7KLLUCtJOPXoVlanhmN0J+ HPIbSBQw/mpL6XhbUfhAtG1njNxO7boTkXVCpwdmpOLPNUGCTV8txK/GkAA0NTTo IfDYmTYN8byoMtrVS84eVF6OyS+1/e1BrYlec= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=kewGsc9uzC+YYgZRvUJfUge8Vo1pno8Y SlbQHI8o/aYl4+NrcvwFWxC8r4Py1nTi2Fpz/LmbpPkIq8jBMs/0zeC+zbbEQcTR RBD0y+3VfHeiEBkLpqiJpA3EhrK5oYn2frg8IEbCNa8++jnARiBxbThDIEEIkxE0 +wM8AFk/jYw= Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id 25F6CFA01B; Tue, 8 Dec 2020 22:22:36 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.75.7.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id 6D37BFA01A; Tue, 8 Dec 2020 22:22:33 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Elijah Newren Cc: Sergey Organov , Jeff King , Philip Oakley , Git Mailing List Subject: Re: [PATCH 00/26] git-log: implement new --diff-merge options References: <20201101193330.24775-1-sorganov@gmail.com> <87y2i8dptj.fsf@osv.gnss.ru> <87y2i8c4mr.fsf@osv.gnss.ru> Date: Tue, 08 Dec 2020 19:22:31 -0800 In-Reply-To: (Elijah Newren's message of "Tue, 8 Dec 2020 19:06:43 -0800") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: C6FF6184-39CD-11EB-9681-E43E2BB96649-77302942!pb-smtp20.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Elijah Newren writes: > ... As I said, I'm not sure why > anyone would ever want to see diffs for merges and not for normal > commits, the closest useful thing I can imagine is commit messages + > diffs for just merges, stripping the normal commits. If I can run "git log --some-options master..next" (or more realistically, over the range ko/next..next) to get individual commits (without patch) and merges (only when --cc gives some interesting nearby-changes), I would be very happy. But is there a set of options that lets me do so?