From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "GIT Mailling list" <git@vger.kernel.org>
Subject: Re: [PATCH] git-daemon server
Date: Fri, 03 Jun 2005 16:56:11 -0400
Date: Fri, 3 Jun 2005 16:49:20 -0400 [thread overview]
Message-ID: <1117832172.8970.22.camel@jmcmullan.timesys> (raw)
In-Reply-To: <Pine.LNX.4.58.0506031320190.1876@ppc970.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Linus, you were wondering why stdin/stdout was the default, even though
I don't have a use case for ssh with stdin/stdout:
1) I used the stdin/stdout stuff as debugging
2) It works with xinetd
3) Because I can't figure out how to get /bin/sh to give me two pipes
that hook together two processes. What I really want:
ssh user@remote git server --db /my/git.git <|> git server request HEAD
Where 'xxx <|> yyy' means:
Take process xxx's stdin, hook it to yyy's stdout,
Take process yyy's stdin, hook it to xxx's stdout,
Run till they both die.
If you know how to do that, I'd be grateful.
--
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-03 20:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 15:22 [PATCH] git-daemon server Jason McMullan
2005-06-03 16:02 ` Linus Torvalds
2005-06-03 16:09 ` McMullan, Jason
2005-06-03 16:30 ` Linus Torvalds
2005-06-03 17:18 ` McMullan, Jason
2005-06-03 17:41 ` Linus Torvalds
2005-06-03 19:30 ` McMullan, Jason
2005-06-03 20:25 ` Linus Torvalds
2005-06-03 20:56 ` McMullan, Jason [this message]
2005-06-03 21:38 ` Linus Torvalds
2005-06-03 22:01 ` Daniel Serpell
2005-06-05 16:44 ` Jason McMullan
2005-06-03 17:00 ` Junio C Hamano
2005-06-03 17:50 ` Linus Torvalds
2005-06-03 17:24 ` Junio C Hamano
2005-06-03 18:30 ` Junio C Hamano
2005-06-03 21:33 ` Daniel Barkalow
2005-06-03 21:59 ` Linus Torvalds
2005-06-03 22:39 ` Petr Baudis
2005-06-04 0:06 ` Daniel Barkalow
2005-06-05 4:47 ` Junio C Hamano
2005-06-05 5:38 ` Daniel Barkalow
2005-06-05 6:48 ` Junio C Hamano
2005-06-05 16:03 ` Daniel Barkalow
2005-06-05 16:17 ` Linus Torvalds
2005-06-05 6:57 ` [PATCH-CAREFUL/RENAME] rename git-rpush and git-rpull to git-ssh-push and git-ssh-pull Junio C Hamano
2005-06-05 16:06 ` Daniel Barkalow
2005-06-05 21:31 ` Linus Torvalds
2005-06-05 22:41 ` Junio C Hamano
2005-06-05 23:17 ` Linus Torvalds
2005-06-05 16:49 ` [PATCH] git-daemon server Jason McMullan
2005-06-05 18:11 ` Linus Torvalds
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=1117832172.8970.22.camel@jmcmullan.timesys \
--to=jason.mcmullan@timesys.com \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).