# HG changeset patch # User Paul Crowley # Date 1255530149 -3600 # Node ID 20b54500a618dda0950ecca3d0b0aba9312e0fb8 # Parent 05b676684c7e83beb5808f9e6f0e5bf210309e67 Call the other user "Sam" diff -r 05b676684c7e -r 20b54500a618 doc/manual.docbook --- a/doc/manual.docbook Wed Oct 14 14:51:45 2009 +0100 +++ b/doc/manual.docbook Wed Oct 14 15:22:29 2009 +0100 @@ -149,7 +149,7 @@ As things stand, no-one but you has any access to any repositories you create on this system. In order to give anyone else access, you'll need a copy of their SSH public key; we'll assume you have that key in -~/other-users-key.pub. You could give them access by +~/sam-key.pub. You could give them access by logging into repository-host, putting the key in the right place under /etc/mercurial-server/keys, and re-running @@ -164,11 +164,11 @@ updating working directory 0 files updated, 0 files merged, 0 files removed, 0 files unresolved jay@my-workstation:~$ cd hgadmin -jay@my-workstation:~/hgadmin$ mkdir -p keys/users/pat -jay@my-workstation:~/hgadmin$ cp ~/other-users-key.pub keys/users/pat/their-workstation +jay@my-workstation:~/hgadmin$ mkdir -p keys/users/sam +jay@my-workstation:~/hgadmin$ cp ~/other-users-key.pub keys/users/sam/their-workstation jay@my-workstation:~/hgadmin$ hg add -adding keys/users/pat/their-workstation -jay@my-workstation:~/hgadmin$ hg commit -m "Add other jay" +adding keys/users/sam/their-workstation +jay@my-workstation:~/hgadmin$ hg commit -m "Add Sam's key'" jay@my-workstation:~/hgadmin$ hg push pushing to ssh://hg@repository-host/hgadmin searching for changes @@ -178,7 +178,7 @@ remote: added 1 changesets with 1 changes to 1 files jay@my-workstation:~/hgadmin$ -The new user can now read and write to your +Sam can now read and write to your ssh://hg@repository-host/repository/name repository. Most other changes to access control can be made simply by making and pushing changes to hgadmin, and you can use Mercurial to