Re: bash completion lacks options

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 8, 2015, 18:38 UTC
Message-ID: <xmqqzj0w7o41.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CACBZZX44qsZZovvJFwP9foqhWaD1ZmL3u+F3hYv2iVq0CKnO6g@mail.gmail.com>

Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:

Show 14 quoted lines

> On Mon, Sep 7, 2015 at 5:36 PM, Olaf Hering <olaf@aepfle.de> wrote:
>> Am 07.09.2015 um 17:34 schrieb Ævar Arnfjörð Bjarmason:
>>> On Mon, Sep 7, 2015 at 5:07 PM, Olaf Hering <olaf@aepfle.de> wrote:
>>
>>>> https://github.com/libguestfs/libguestfs/commit/0306c98d319d189281af3c15101c8d343e400f13
>>>
>>> This is an interesting approach, but wouldn't help with git-send-email
>>> in particular, it's a Perl script, so there's no ELF section to parse.
>>
>> format-patch is a ELF binary, a link to git itself as I notice
>> just now.
>
> Yes, format-patch is written in C, but you mentioned send-email, which
> is a Perl script.

I think Olaf means that send-email has a mode where it can drive format-patch directly from the command line.

This is a slightly related tangent, but I've been wondering if it makes sense to discourage, deprecate and eventually remove that mode of operation. It appears it is the biggest single source of poorly proof-read series, when compared to "format-patch to a directory with --cover option and then give them a final scan before running send-email on them" workflow.