Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: New cvs setup?
Date: Mon, 29 Oct 2001 22:20:44 -0800	[thread overview]
Message-ID: <m18zdtlkcj.fsf@reader.newsguy.com> (raw)
In-Reply-To: <yosu668xitch.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 30 Oct 2001 14:34:35 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Yes I do.  I believe that we have no need to log in for each
> time.
>
>> It appears you are calling a cvs server and running scripts in
>> cvsroot.  Can that happen withoug logging in or some other form of
>> connecting to the machine?
>
> Logging in procedure is necessary only when the entry for the
> server is not in the file ~/.cvspass or the password has
> changed.  However,

Sorry Katsumi.  I was using the term login to loosely.  I really meant
some method of connecting to the server.  Its happening from your
~/.cvspass file but none the less a handshake is taking place and info
is being exchanged.  Thats the part I'm not able to do.

Thanks for your help.  I learned a little about cvs just from looking
at your usage.  If this doesn't clear up by tomorrow. I will assume it
isn't just internet noise problems.

My traceroute gets to an Oslo network in Norway before the " * * *"
starts.
15  oslo-a1.enitel.net (194.19.1.112)  257.443 ms  261.563 ms  258.211
ms
16  194.19.90.66 (194.19.90.66)  242.419 ms  243.956 ms  243.440 ms
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *

But did you say the server won't accept traceroute packets anyway?



  parent reply	other threads:[~2001-10-30  6:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  0:18 Harry Putnam
2001-10-30  0:53 ` Katsumi Yamaoka
2001-10-30  1:56   ` Harry Putnam
2001-10-30  2:12     ` Katsumi Yamaoka
2001-10-30  2:30       ` Harry Putnam
2001-10-30  2:45         ` Katsumi Yamaoka
2001-10-30  3:39           ` Harry Putnam
2001-10-30  4:06             ` Katsumi Yamaoka
2001-10-30  5:03               ` Harry Putnam
2001-10-30  5:34                 ` Katsumi Yamaoka
2001-10-30  5:41                   ` Katsumi Yamaoka
2001-10-30  6:20                   ` Harry Putnam [this message]
2001-10-30  7:09                     ` Katsumi Yamaoka
2001-10-30 13:57                     ` news
2001-10-30 14:48                       ` Harry Putnam
2001-10-30 15:03                       ` Harry Putnam
2001-10-30 16:40                         ` Robert Epprecht
2001-10-30 15:27                     ` Dan Christensen
2001-10-30 17:27                       ` Harry Putnam
2001-10-30 17:40                         ` Richard Hoskins
2001-10-30 19:26                           ` Harry Putnam
2001-10-30 19:37                           ` Josh Huber
2001-10-30 20:07                             ` Harry Putnam
2001-10-30 20:25                               ` Paul Jarc
2001-10-30 21:19                                 ` Josh Huber
2001-10-30 21:46                                   ` Matt Armstrong
2001-10-31  3:01                                     ` Harry Putnam
2001-10-31  4:57                                       ` Paul Jarc
2001-10-30 21:59                             ` Robert Epprecht

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=m18zdtlkcj.fsf@reader.newsguy.com \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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.
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).