From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Junio C Hamano <gitster@pobox.com>,
"Horst H. von Brand" <vonbrand@inf.utfsm.cl>,
git@vger.kernel.org
Subject: Re: [PATCH] git-pull.sh: Fix call to git-merge for new command format
Date: Wed, 02 Dec 2009 08:45:36 -0800 [thread overview]
Message-ID: <7vws15jpe7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4B163B49.4070606@drmicha.warpmail.net> (Michael J. Gruber's message of "Wed\, 02 Dec 2009 11\:02\:49 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> This made me wonder a bit: Do we have a policy regarding the use of
> "git-command" vs. "git command" in git shell scripts such as this one?
Yes. Anything that sets GIT_EXEC_PATH correctly can use git-foo form.
next prev parent reply other threads:[~2009-12-02 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 22:44 [PATCH] git-pull.sh: Fix call to git-merge for new command format Horst H. von Brand
2009-12-01 23:54 ` Junio C Hamano
2009-12-02 10:02 ` Michael J Gruber
2009-12-02 16:45 ` Junio C Hamano [this message]
2009-12-02 17:29 ` Michael J Gruber
2009-12-02 17:49 ` Junio C Hamano
2009-12-03 8:10 ` Michael J Gruber
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=7vws15jpe7.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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).