From: "Christopher R. Johnson" <cjohnson@gcctech.com>
To: "Kerl, John" <John.Kerl@Avnet.com>
Cc: song sam <samsongshzu@yahoo.com.cn>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Which kernel tree
Date: Fri, 06 Feb 2004 12:00:48 -0500 [thread overview]
Message-ID: <4023C840.5070002@gcctech.com> (raw)
In-Reply-To: C7FFFEA58B43D311920D0004ACE5333F10E4F57B@amer25.avnet.com
In this type of situation, using cvs over ssh is a better solution.
Google it. I think Apache developers have to do this these days.
Check out:
http://xml.apache.org/forrest/community/howto/cvs-ssh/howto-cvs-ssh.html
Kerl, John wrote:
>I also cannot use CVS from behind a firewall, but it is not
>the fault of CVS. Since I use CVS only infrequently, I ssh
>out from my firewall to a node outside my firewall, run cvs
>from there, and sftp the resulting tree back behind my firewall.
>For infrequent use, this might be an acceptable setup.
>
>-----Original Message-----
>From: Wolfgang Denk [mailto:wd@denx.de]
>Sent: Friday, February 06, 2004 9:01 AM
>To: song sam
>Cc: linuxppc-embedded@lists.linuxppc.org
>Subject: Re: Which kernel tree
>
>
>
>Dear Sam,
>
>in message <20040206155027.83638.qmail@web15211.mail.bjs.yahoo.com> you
>wrote:
>
>>>There is also linuxppc_2_4_devel on our CVS server,
>>>which is 2.4.24-preX
>>>
>>But how to make it?I used WinCvs in WIN2000 and CVS
>>command in REDHAT 7.3 as
>>cvs -d :pserver:anonymous@www.denx.de:/cvsroot login
>>but couldn't connect.If I use proxty like
>>
>
>I cannot comment on WinCvs (as I've never worked under Windoze), but
>CVS in RH-7.3 will certainly work.
>
>Are you sure that it's not some other configuration on your end which
>is preventing CVS from working? Like a firewall blocking the CVS port
>(2401) ?
>
>>172.12.18.1:8080 which I can login your webpage,how
>>could I get to linuxppc_2_4_devel?
>>
>
>Use CVS. It works.
>
>Best regards,
>
>Wolfgang Denk
>
>--
>See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
>Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
>Do not follow where the path may lead....go instead where there is no
>path and leave a trail.
>
>
>
--
Christopher R. Johnson
Principal Software Engineer
GCC Printers
(781)276-8763
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-06 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 16:06 Which kernel tree Kerl, John
2004-02-06 17:00 ` Christopher R. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 3:01 Stephen Williams
2004-02-06 3:11 ` Eugene Surovegin
2004-02-06 3:56 ` Stephen Williams
2004-02-06 8:37 ` Andrei Konovalov
2004-02-06 7:42 ` Wolfgang Denk
2004-02-06 15:50 ` song sam
2004-02-06 16:00 ` Wolfgang Denk
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=4023C840.5070002@gcctech.com \
--to=cjohnson@gcctech.com \
--cc=John.Kerl@Avnet.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=samsongshzu@yahoo.com.cn \
/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).