From: christian@j-son.org
To: binutils@sources.redhat.com
Subject: Re: cvs access via ssh?
Date: Wed, 05 May 2004 05:15:00 -0000 [thread overview]
Message-ID: <20040505051550.GB2077@pentium3.j-son.org> (raw)
In-Reply-To: <m3brl33ala.fsf@gossamer.airs.com>
On Tue, May 04, 2004 at 09:51:29PM -0400, Ian Lance Taylor wrote:
> Christian Joensson <christian@j-son.org> writes:
>
> > Just an idea here... would it make sense to have the binutils sources
> > (and friends?) available via ssh also (as is gcc from savannah these
> > days)?
>
> What would be the advantage of doing that?
mainly to be able to access the cvs trees from behind firewalls that
won't let :pserver through....
> I'm not absolutely opposed to it, but it seems to me that it would
> lead to more load on the server, which is already struggling along at
> the best of times.
>
> The place to suggest a change like this is overseers@sourceware.org.
sure, just checking opinions here first...
Cheers,
/ChJ
prev parent reply other threads:[~2004-05-05 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 10:56 Christian Joensson
2004-05-05 1:51 ` Ian Lance Taylor
2004-05-05 5:14 ` christian
2004-05-05 5:15 ` christian [this message]
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=20040505051550.GB2077@pentium3.j-son.org \
--to=christian@j-son.org \
--cc=binutils@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).