readme.txt #3

This is a test Perforce Helix DVCS repo to see what happens when I try
to push it up to Ravenbrook's main perforce server.

So far it's just:

    p4 init
    vi readme.txt
    p4 add readme.txt
    p4 submit

Then we'll see.

---

That seemed to work.

I pushed the repo up to perforce.ravenbrook.com by createing a remote spec
for perforce.ravenbrook.com with p4 remote, then did p4 push -r ravenbrook -v.

rb@Silverbird$ p4 push -r ravenbrook -v
Change 1 imported as change 189000.
File //info.ravenbrook.com/user/rb/sandbox/2016-01-27/pushup/stream/main/readme.txt#1 imported as #1.
Resource usage: qry/zip/db/arch/fin/tot=22ms/0ms/569ms+898B/99ms+398B/351ms/1s

I then set up a local test server.  I had to force it to be case sensitive
because HFS+ is not by default.

    mkdir p4push-server
    cd p4push-server
    p4d -r . -C0
    p4 -p localhost:1666 configure set server.allowpush=2

Then I set up another remove called localtest talking to localhost:1666
and pushed to that too.  Seemed to work.  This edit is being made on the
Ravenbrook server to check how pulling from there and pushing to the
local test server will work.

---

I was able to create a remote to the Perforce Public Repo, push
this up there, and see the results at
<https://swarm.workshop.perforce.com/files/guest/richard_brooksby/sandbox/2016-01-27/p4push/stream/main/readme.txt>
so this could be used for publishing/sharing stuff with the Perforce
community.

Neat.