linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: linuxppc-dev@lists.linuxppc.org, linuxppc-commit@source.mvista.com
Subject: PPC bk repos reorg
Date: Thu, 9 Aug 2001 19:28:52 -0700	[thread overview]
Message-ID: <20010809192852.L13789@work.bitmover.com> (raw)
In-Reply-To: <15218.7077.297813.862317@cargo.ozlabs.ibm.com>; from paulus@samba.org on Thu, Aug 09, 2001 at 03:12:05PM +1000


The hosting service has evolved.  You need to be running the latest
and greatest to make the following work.  The old port number based
anon access will continue for now but will go away, switch your parent
pointers please.

Summary of changes:

a) The admin login is "ppc.adm", it used to be "ppc".
b) The ssh login is "ppc", it used to be "ppc.<repo>"
c) URL changes
   Old anonymous:
	bk://ppc.bitkeeper.com:5000..5004 these are going away
   New anonymous:
	bk://ppc.bkserver.net/linux_2_2
	bk://ppc.bkserver.net/linux_2_4
	etc.
   Old ssh:
	bk://ppc.linux_2_2@bitkeeper.com
   New ssh:
	bk://ppc@ppc.bkserver.net/linux_2_2
	bk://ppc@ppc.bkserver.net/linux_2_4

Notes:
    * The domain name has changed, it is now ppc.bkserver.net.  Please use
      the new name, the old one will go away.
    * You may figure out that we are just aliasing ppc.<bunch of domains>
      to the same place and decide that bk://ppc@bkserver.net/linux_2_4 is
      shorter.  That will work until the day that we are too loaded to host
      all this on one machine and we change dns to point ppc.bkserver.net
      to some other machine.  So use the full name, you only have to do it
      when you set up a repo and then BK remembers it.
--
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2001-08-10  2:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15218.2656.8980.846399@cargo.ozlabs.ibm.com>
     [not found] ` <20010808211410.J7728@work.bitmover.com>
     [not found]   ` <15218.4778.270562.782105@cargo.ozlabs.ibm.com>
     [not found]     ` <20010808213806.C13789@work.bitmover.com>
     [not found]       ` <15218.7077.297813.862317@cargo.ozlabs.ibm.com>
2001-08-10  2:28         ` Larry McVoy [this message]
2001-08-10  4:21           ` PPC bk repos reorg Paul Mackerras
2001-08-10 15:07           ` Tom Rini
2001-08-10 15:16             ` Larry McVoy
2001-08-13 13:43               ` Gavin Hemphill
2001-08-13 15:35                 ` Larry McVoy
2001-08-14 11:54                   ` Kenneth Johansson

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=20010809192852.L13789@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linuxppc-commit@source.mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.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).