From: Junio C Hamano <gitster@pobox.com>
To: dherring@ll.mit.edu
Cc: git@vger.kernel.org
Subject: Re: docs and completion and dashless commands
Date: Fri, 22 Aug 2008 14:34:05 -0700 [thread overview]
Message-ID: <7vr68g7n02.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.0.999999.0808221550100.11892@mojave> (dherring@ll.mit.edu's message of "Fri, 22 Aug 2008 16:26:32 -0400 (EDT)")
dherring@ll.mit.edu writes:
> First off, I'm not too keen on these dashless commands.
> - We now have `man git-X` but can't run `git-X`
> - A separate completion script must be installed for bash
> - Lose completion for all other shells
> - History expansion is complicated (e.g. `!git-push` vs `!git push`)
Please stop and leave the dead horse lie in piece. You are more than a
year too late.
> Anyway, could someone modify INSTALL to mention
> contrib/completion/git-completion.bash and putting `git --exec-path`
> in PATH for other shells?
And please nobody waste time on the latter. "git-foo" form for builtins
will be removed from the filesystem eventually and at that point:
#!/bin/sh
PATH=$(git --exec-path):$PATH
.. do its thing ..
git-commit -a -m 'funny wrapper created commit'
will _stop_ working. If somebody is starting a new script there is no
point using the form only to later update to the dashless form.
> These docs might also instruct users to call
> git-config and set their global username and email.
Please read the first few paragraphs of gittutorial(7).
prev parent reply other threads:[~2008-08-22 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 20:26 docs and completion and dashless commands dherring
2008-08-22 21:34 ` Junio C Hamano [this message]
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=7vr68g7n02.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dherring@ll.mit.edu \
--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).