From: Johannes Sixt <j6t@kdbg.org>
Date: Tue, 24 Jan 2017 07:15:56 GMT
Subject: Re: [PATCH 7/7] completion: recognize more long-options
Message-ID: <74ecd09c-55da-3858-5187-52c286a6bf62@kdbg.org>
In-Reply-To: <20170122225724.19360-8-cornelius.weig@tngtech.com>

If at all possible, please use your real email address as the From 
address. It is pointless to hide behind a fake address because as Git 
contributor you will have to reveal your identity anyway.

Please study item (5) "Sign your work" in 
Documentation/SubmittingPatches and sign off your work.

I'm by no means a bash completion expert, but I have a comment on this 
patch.

Am 22.01.2017 um 23:57 schrieb bitte.keine.werbung.einwerfen@googlemail.com:
> Recognize several new long-options for bash completion in the following
> commands:

AFAIR, it was a deliberate decision that potentially destructive command 
line options are not included in command completions. In the list given, 
I find these:

>  - apply: --unsafe-paths
>  - reset: --merge --mixed --hard --soft --patch --keep
>  - rm: --force

Additionally, these options are only for internal purposes, but I may be 
wrong:

>  - archive: --remote= --exec=

-- Hannes