From: Olaf Hering <olaf@aepfle.de>
To: git@vger.kernel.org
Subject: bash completion lacks options
Date: Mon, 7 Sep 2015 17:07:58 +0200 [thread overview]
Message-ID: <20150907150757.GA6720@aepfle.de> (raw)
"git send-email --f<tab>" lacks --find-renames and others. Is the list
of possible options maintained manually? Perhaps this should be
automated by placing the long strings in an ELF section, then filling
variables like $__git_format_patch_options from such ELF section.
An example how this was done in libguestfs is here (see daemon/daemon.h):
https://github.com/libguestfs/libguestfs/commit/0306c98d319d189281af3c15101c8d343e400f13
Olaf
next reply other threads:[~2015-09-07 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 15:07 Olaf Hering [this message]
2015-09-07 15:34 ` bash completion lacks options Ævar Arnfjörð Bjarmason
2015-09-07 15:36 ` Olaf Hering
2015-09-08 11:28 ` Ævar Arnfjörð Bjarmason
2015-09-08 12:49 ` Olaf Hering
2015-09-08 18:38 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150907150757.GA6720@aepfle.de \
--to=olaf@aepfle.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).