Linux PARISC architecture development
 help / color / mirror / Atom feed
From: dann frazier <dannf@dannf.org>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] cvs migration
Date: Wed, 28 May 2003 00:42:50 -0600	[thread overview]
Message-ID: <20030528064250.GA29360@dannf.org> (raw)

cvs has moved to our new box (finally! hosted on a parisc-linux box!)
if you've been using the recommended cvs.parisc-linux.org name, the transition
should have been transparent, in most regards.

- anonymous access should be transparent.
- ssh users that weren't part of willy's list of recent committers will need
  to request their account be reactivated.
- ssh users will see that the host key has changed.
- you may get errors until dns propogation has completed
- non-cvs accounts from dsl2 have not migrated to palinux, nor have home
  directories.  home directories should be migrated by hand.
- bame: your cronjobs that access cvs will likely break - sorry for the lack
  of warning.

please let me know if you notice other breakages (i'm not on this list).

-- 

dannf@dannf.org 

             reply	other threads:[~2003-05-28  6:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28  6:42 dann frazier [this message]
     [not found] ` <3ED467BB.90204@bluehash.de>
2003-05-28 14:56   ` [parisc-linux] cvs migration dann frazier

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=20030528064250.GA29360@dannf.org \
    --to=dannf@dannf.org \
    --cc=parisc-linux@lists.parisc-linux.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