From: Junio C Hamano <gitster@pobox.com>
To: Jason Riedy <jason@acm.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Pass --upload-pack and --receive-pack through submodules.
Date: Thu, 01 Jan 2009 13:00:50 -0800 [thread overview]
Message-ID: <7vy6xuhhbx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1230649782-14710-1-git-send-email-jason@acm.org
Jason Riedy <jason@acm.org> writes:
> While I no longer have to worry about a zillion ancient OS versions,
> I now have to worry about a remote site where I cannot control the
> path for non-interactive shells. Thus, submodules need to handle
> explicitly specified git-upload-pack and git-receive-pack programs.
Do we (and can we) assume that the remote repositories submodules fetch
from all reside on the same host and can share the same values for these
parameters? Shouldn't these instead be specified in the configuration
files for the submodules, if they need to be nonstandard values?
next prev parent reply other threads:[~2009-01-01 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 2:44 [PATCH] Pass --upload-pack and --receive-pack through submodules Jason Riedy
2008-12-30 15:09 ` Jason Riedy
2009-01-01 21:00 ` Junio C Hamano [this message]
2009-01-02 1:44 ` Jason Riedy
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=7vy6xuhhbx.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jason@acm.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).