unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jaime E . Villate" <villate@gnu.org>
Cc: "Kim F. Storm" <storm@cua.dk>
Subject: Re: [alexl@users.sourceforge.net: Jan's Gtk CVS notifications...?]
Date: Thu, 23 Jan 2003 18:39:37 +0000	[thread overview]
Message-ID: <20030123183937.P397@fe.up.pt> (raw)
In-Reply-To: <m3hebzwzky.fsf@gnu.org>; from yeupou@gnu.org on Thu, Jan 23, 2003 at 06:22:37PM +0100

On Thu, Jan 23, 2003 at 06:22:37PM +0100, Mathieu Roy wrote:
> storm@cua.dk (Kim F. Storm) said:
> 
> > I'm that kfstorm, and would like to adapt to the new repository.
> > So I tried this:
> > 
> > cvs -d :pserver:kfstorm@subversions.gnu.org:/cvsroot/emacs co -d emacs emacs
> > with a negative response:
> 
> Normally pserver is used for anonymous access.
> 
> With a usual ssh account, you just have to try something like
> cvs -z3 -d kfstorm@subversions.gnu.org:/cvsroot/emacs co emacs
> 
> With a kerberos account, it should be something like
> cvs -z3 -d :gserver:kfstorm@subversions.gnu.org:/cvsroot/emacs co emacs

Yes, I'm sorry I said something that is not true; the new repository does not
have the same access methods of the old one, since pserver is now only allowed
for anonymous users (in which case there is no harm by sending passwords over
the Internet). Developers must use SSH to access the new CVS repository, as
Mathieu explained.

To configure your SSH access, please read:

http://savannah.gnu.org/faq/?group_id=11&question=How_do_I_configure_my_SSH_access.txt

Cheers,
Jaime

  reply	other threads:[~2003-01-23 18:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E18bcI9-0007hg-00@fencepost.gnu.org>
2003-01-23 12:00 ` [Savannah-hackers] [alexl@users.sourceforge.net: Jan's Gtk CVS notifications...?] Jaime E. Villate
2003-01-23 13:58   ` Juanma Barranquero
2003-01-23 14:57     ` Jaime E. Villate
2003-01-23 23:24     ` Kenichi Handa
2003-01-24  1:26       ` Jaime E . Villate
2003-01-24 13:12         ` Kim F. Storm
2003-01-24 18:54           ` Eli Zaretskii
2003-01-24 21:44             ` Kim F. Storm
2003-01-25 16:56               ` Eli Zaretskii
2003-01-25 18:08                 ` Rudy Gevaert
2003-01-25 17:19                   ` Eli Zaretskii
2003-01-25 18:28                     ` Rudy Gevaert
2003-01-26  5:46                       ` Eli Zaretskii
2003-01-25 18:16                 ` Mathieu Roy
2003-03-12 19:11                   ` Eli Zaretskii
2003-01-26 15:37             ` [Savannah-hackers] " Richard Stallman
2003-01-27 10:29               ` Jaime E. Villate
2003-01-29  0:04                 ` Richard Stallman
2003-01-25 19:23           ` Richard Stallman
2003-01-24 10:50     ` Juanma Barranquero
2003-01-23 18:06   ` Kim F. Storm
2003-01-23 17:22     ` Mathieu Roy
2003-01-23 18:39       ` Jaime E . Villate [this message]
2003-01-24 17:15   ` [Savannah-hackers] " Richard Stallman
2003-01-22  2:51 Jan's Gtk CVS notifications...? Alex Lancaster
2003-01-23  8:00 ` Richard Stallman
2003-01-23 18:22 ` Jan D.

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030123183937.P397@fe.up.pt \
    --to=villate@gnu.org \
    --cc=storm@cua.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).