git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Serpell <daniel.serpell@gmail.com>
To: GIT Mailling list <git@vger.kernel.org>
Subject: Re: [PATCH] git-daemon server
Date: Fri, 3 Jun 2005 18:01:06 -0400	[thread overview]
Message-ID: <f0796bb7050603150168c1db95@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506031410560.1876@ppc970.osdl.org>

On 6/3/05, Linus Torvalds <torvalds@osdl.org> wrote:
> 
> On Fri, 3 Jun 2005, McMullan, Jason wrote:
> >
> > 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
> 
> Ok, so a ssh connection _would_ work per se, and the only real issue is
> the pipe itself is one-directional as done by the shell?
> 
[...]
> Anyway, with _something_ like the above you could do something like
> 
>         git-sync --exec "ssh master.kernel.org git-sync" ....
> 
> and it would do the obvious thing.
> 

I would prefer a command line more like the rsync one:
       git-sync master.kernel.org:directory  ....

Or:
       git-sync :ssh:master.kernel.org:directory  ....

Or "uri like":
       git-sync ssh://mylogin@master.kernel.org/directory  ....

It seems much easier, and I suppose that SSH should be the
default "developer" protocol.

     Daniel.

  reply	other threads:[~2005-06-03 21:57 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
2005-06-03 21:38                 ` Linus Torvalds
2005-06-03 22:01                   ` Daniel Serpell [this message]
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=f0796bb7050603150168c1db95@mail.gmail.com \
    --to=daniel.serpell@gmail.com \
    --cc=git@vger.kernel.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).