From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Sam Song <samlinuxkernel@yahoo.com>
Cc: Petr Vandrovec <petr@vmware.com>, git@vger.kernel.org
Subject: Re: Fwd: [OT] Re: Git via a proxy server?
Date: Wed, 17 May 2006 10:38:45 +0200 [thread overview]
Message-ID: <20060517083845.GC23642@lug-owl.de> (raw)
In-Reply-To: <20060517035639.40450.qmail@web32004.mail.mud.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Tue, 2006-05-16 20:56:39 -0700, Sam Song <samlinuxkernel@yahoo.com> wrote:
> Petr Vandrovec <petr@vmware.com> wrote:
> > Best to test this is to start 'socket 192.168.40.99
> > 80' from command line and
> > then type these two lines above, plus one empty
> > line. You should get back '200
> > OK', empty line, and then you can start
> > communicating using git protocol - if
> > you can do that...
>
> I cannot run "socket" and "CONNECT" on Fedora Core 3.
> It simply told me that no such command. How could I
> do this task in my case?
Well, install some package to have `socket' available? Debian calls
the packet `socket', too, so I guess Fedora may have something
similar.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-17 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 12:13 Fwd: [OT] Re: Git via a proxy server? Sam Song
2006-05-16 13:11 ` Petr Vandrovec
2006-05-17 3:56 ` Sam Song
2006-05-17 8:38 ` Jan-Benedict Glaw [this message]
2006-05-17 10:54 ` Petr Vandrovec
2006-05-18 3:44 ` Sam Song
2006-05-18 8:31 ` Jan-Benedict Glaw
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=20060517083845.GC23642@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=git@vger.kernel.org \
--cc=petr@vmware.com \
--cc=samlinuxkernel@yahoo.com \
/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).