Thread (23 messages) flat view 23 messages, 4 authors, 2017-02-09

Re: [PATCH 7/7] completion: recognize more long-options

From: Johannes Sixt <hidden>
Date: 2017-01-24 07:16:05

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help