<nanako3@xxxxxxxxxxx> wrote:
> Quoting Junio C Hamano <gitster@xxxxxxxxx>:
> > Miklos Vajna <vmiklos@xxxxxxxxxxxxxx> writes:
> >> On Tue, Jun 24, 2008 at 04:16:36PM -0700, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> >>> It most likely makes sense to do (3) anyway. upload-pack, receive-pack,
> >>> anything else?
> >>
> >> I think that's all.
> >
> > Then that would be this patch on top of nd/dashless topic.
> >
> > Makefile | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/Makefile b/Makefile
> > index 929136b..babf16b 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -1268,7 +1268,7 @@ install: all
> > $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(bindir_SQ)'
> > $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(gitexecdir_SQ)'
> > $(INSTALL) $(ALL_PROGRAMS) '$(DESTDIR_SQ)$(gitexecdir_SQ)'
> > - $(INSTALL) git$X '$(DESTDIR_SQ)$(bindir_SQ)'
> > + $(INSTALL) git$X git-upload-pack$X git-receive-pack$X '$(DESTDIR_SQ)$(bindir_SQ)'
> > $(MAKE) -C templates DESTDIR='$(DESTDIR_SQ)' install
> > $(MAKE) -C perl prefix='$(prefix_SQ)' DESTDIR='$(DESTDIR_SQ)' install
> > ifndef NO_TCLTK
>
> Doesn't "git archive --remote=<repo>" also execute git program on a remote machine?
Yes, it runs git-upload-archive on the remote side. The three
primary services for the remote side are documented in daemon.c:
403 static struct daemon_service daemon_service[] = {
404 { "upload-archive", "uploadarch", upload_archive, 0, 1 },
405 { "upload-pack", "uploadpack", upload_pack, 1, 1 },
406 { "receive-pack", "receivepack", receive_pack, 0, 1 },
407 };
(with git- prefixes).
IMHO all three need to be in $PATH, along with git and gitk, through
at least a major revision release cycle to give clients a chance to
upgrade to something that uses "git foo" rather than "git-foo" when
talking to the remote.
--
Shawn.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
