Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: New cvs setup?
Date: Tue, 30 Oct 2001 14:34:35 +0900	[thread overview]
Message-ID: <yosu668xitch.fsf@jpl.org> (raw)
In-Reply-To: <m1668xn2j4.fsf@reader.newsguy.com>

>>>>> In <m1668xn2j4.fsf@reader.newsguy.com>
>>>>>	Harry Putnam <reader@newsguy.com> wrote:

>>>> if (`cvs -d :pserver:gnus@cvs.gnus.org:/usr/local/cvsroot\\
>>>>  status gnus/lisp/ChangeLog|& grep '^File: ChangeLog'| wc -l` == 1) then

> You mean you can check status of files and grep through ChangeLogs
> without logging in?

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,

>> Is your `cvs' a real cvs executable?

> rpm -q cvs
> cvs-1.11-3

> Its the same cvs I've been updating with for mnths.  For example

>> Otherwise, there seems to be something wrong in your environment
>> (e.g. firewall).

> I don't think so.

[...]

> I'm not very adept at using cvs but, my executable seems to be
> working in all cases but gnus.  That should in theory, rule out a
> firewall or networking misconfiguration.

There seems to be no problem in your environment, but I don't
know what is the matter.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



  reply	other threads:[~2001-10-30  5:34 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 [this message]
2001-10-30  5:41                   ` Katsumi Yamaoka
2001-10-30  6:20                   ` Harry Putnam
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=yosu668xitch.fsf@jpl.org \
    --to=yamaoka@jpl.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).