README_REPOSITORY
changeset 28918 eda3d9976ec7
parent 28917 20f43e0e0958
child 29481 3e8420c1124a
     1.1 --- a/README_REPOSITORY	Sun Nov 30 14:43:29 2008 +0100
     1.2 +++ b/README_REPOSITORY	Sun Nov 30 15:03:47 2008 +0100
     1.3 @@ -21,13 +21,12 @@
     1.4  yet retrieve any changesets that have escaped into the public by
     1.5  accident.
     1.6  
     1.7 -Only global operations like "pull" / "push", "unbundle" / "bundle"
     1.8 -etc. fall into this critical category.  Note that "incoming" /
     1.9 -"outgoing" allow to inspect changesets before exchanging them
    1.10 -globally.  Anything else in Mercurial is local to the user's
    1.11 -repository clone (including "commit", "update", "merge" etc.) and is
    1.12 -in fact much simpler and safer to use than the corresponding
    1.13 -operations of CVS or SVN.
    1.14 +Only global operations like "pull" and "push" fall into this critical
    1.15 +category.  Note that "incoming" / "outgoing" allow to inspect
    1.16 +changesets before exchanging them globally.  Anything else in
    1.17 +Mercurial is local to the user's repository clone (including "commit",
    1.18 +"update", "merge" etc.) and is in fact much simpler and safer to use
    1.19 +than the corresponding operations of CVS or SVN.
    1.20  
    1.21  
    1.22  Initial configuration
    1.23 @@ -57,7 +56,7 @@
    1.24    username = wenzelm
    1.25  
    1.26  Of course, the user identity can be also configured in
    1.27 -isabelle/.hg/hgrc on per-repitory basis.  Failing to specify the
    1.28 +isabelle/.hg/hgrc on per-repository basis.  Failing to specify the
    1.29  username correctly makes the system invent funny machine names that
    1.30  may persist indefinitely in the public flow of changesets.
    1.31