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: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,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 407421F8C8 for ; Sat, 25 Sep 2021 04:07:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230070AbhIYEJO (ORCPT ); Sat, 25 Sep 2021 00:09:14 -0400 Received: from pb-smtp2.pobox.com ([64.147.108.71]:62234 "EHLO pb-smtp2.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229516AbhIYEJM (ORCPT ); Sat, 25 Sep 2021 00:09:12 -0400 Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id B76A1D480F; Sat, 25 Sep 2021 00:07:37 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=0zbSNKTuSDBpZi/2S18P5FK3U7UzxTsC5AbBpZ g8E0o=; b=WUajJ/6LMy5yQsYg0qgU7k5jVaa24DDGUWuRMuuDgRL9GJAmogKos7 MuMh1CJOSaPXb0tjPLo9ARok1R6aB7CKehBf42JxwLB4eA5ryrxzeEzENlYS/jIZ 99ZUElDVr05tiewIOiOCJXbs7F7TNtJDpTBdBQjn7G8yNuLS1OX9E= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 9B42BD480E; Sat, 25 Sep 2021 00:07:37 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [104.133.2.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id E65BBD480C; Sat, 25 Sep 2021 00:07:36 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Bagas Sanjaya Cc: Carlo Arenas , Thiago Perrotta , avarab@gmail.com, git@vger.kernel.org Subject: Re: [PATCH v5 3/3] send-email docs: add format-patch options References: <87zgs34ccx.fsf@evledraar.gmail.com> <20210924024606.20542-4-tbperrotta@gmail.com> <9a60226c-7a35-0486-a687-31f7691e7551@gmail.com> Date: Fri, 24 Sep 2021 21:07:35 -0700 In-Reply-To: (Bagas Sanjaya's message of "Sat, 25 Sep 2021 10:03:01 +0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 1E33E296-1DB6-11EC-9EAE-CD991BBA3BAF-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Bagas Sanjaya writes: > On 25/09/21 03.03, Junio C Hamano wrote: >> Ah, thanks for explanation. >> git format-patch -2 >> would be options-only way to "indicate some sort of revision", so >> perhaps >> . git send-email files|directory >> . git send-email >> (where "options" is used to refer to both --options and arguments) >> would illustrate the differences better? >> > > But we can also directly specify revision range (commonly ancestor>..HEAD or HEAD ^). That is exactly why I have the parenthetical definition of what "options" mean in my explanation. git format-patch -2 git format-patch master git format-patch master..HEAD Everything after "git format-patch", i.e. -2, master, master..HEAD, are usable, and there isn't much point in singling out revision ranges. FWIW, I think you can even give "-- " at the end, which are not options or revision ranges.