all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: [Savannah-hackers] [alexl@users.sourceforge.net: Jan's Gtk CVS notifications...?]
Date: Sat, 25 Jan 2003 19:56:07 +0300	[thread overview]
Message-ID: <7458-Sat25Jan2003195606+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <5xwuku5ijy.fsf@kfs2.cua.dk> (storm@cua.dk)

> From: storm@cua.dk (Kim F. Storm)
> Date: 24 Jan 2003 22:44:49 +0100
> 
> > I don't use CVS/ssh, and cannot easily do so.  If the old repository
> > is eliminated, I will have no way to check in changes, not even by
> > logging into gnu.org machines (since my login there is effectively
> > disabled by the requirement to install SSHv2 clients).
> > 
> 
> CVS access uses ssh v1.

Yes, I know that.  What I meant to say is that my home machine runs
Windows, where I have a CVS port installed that doesn't support SSH at
all.  That port is well configured and set up, and served me well for
2 years; I'm accustomed to it, including a couple of Windows-related
quirks.  Given the total lack of free time, I cannot afford installing
and configuring another port, even if it's not the Cygwin port (the
latter would mean I also need to install gobs of related and
semi-related packages I don't really need, which will interfere with
my system setup that is not based on Cygwin).

Installing a free OS is also impractical, for the same reasons: I
simply don't have enough time to become a full-time system manager for
an OS of which my current knowledge level is at best that of a
sophisticated user.

I do have a working SSHv1 setup on my home machine that supports
telnet and scp, so I could remedy the problem with CVS by logging into
gnu.org and committing changes from there.  However, that approach,
too, was closed to me when gnu.org went to SSHv2.  Moving to SSHv2 on
my home machine would again require installing, configuring, and
learning to use packages for which I don't have time.

> > However, since lately I seldom check in anything, I'm not sure you
> > should keep the old repository just for my sake.
> 
> Sorry I jumped to conclusions...  but as I understand the message from
> Jaime, it is only a question of time before the :pserver: write access
> is disabled...

Yes, I knew that for some time now.  That's why I'm not sure my
problems are important enough for you to avoid doing that now.

  reply	other threads:[~2003-01-25 16:56 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=7458-Sat25Jan2003195606+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.