Re: [PATCH RFC] new config option remote.<name>.pushexec
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 16, 2007, 20:30 UTC
- Message-ID
- <Pine.LNX.4.63.0701162129430.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <20070116200847.GB29100@spearce.org>
Hi,
On Tue, 16 Jan 2007, Shawn O. Pearce wrote:
Show 21 quoted lines
> Uwe Kleine-K?nig <zeisberg@informatik.uni-freiburg.de> wrote: > > Exactly. Quoting git-send-pack(1): > > > > Path to the git-receive-pack program on the remote end. > > Sometimes useful when pushing to a remote repository over ssh, > > and you do not have the program in a directory on the default > > $PATH. > > > > For me it would be: > > > > pushexec = /home/zeisberg/usr/bin/git-receive-pack > > > > While having /home/zeisberg/usr/bin only in my PATH for interactive > > shells. (Yes I know I could expand my PATH which .<someshrc>, but I'd > > prefer it that way.) > > Some of us have UNIX accounts where our shell is the (retarded) > /usr/bin/ksh on Solaris. And where the SSH daemon won't seem to > let us set PATH, and where Git isn't in the PATH. This leaves > us with some difficulty in pointing Git at itself on the remote > system.
Okay, I see your point now.
Ciao, Dscho