##// END OF EJS Templates
Update the README a bit
mpm@selenic.com -
r160:5c331d94 default
parent child Browse files
Show More
@@ -20,9 +20,9 b' Setting up a Mercurial project:'
20 20 $ hg init # creates .hg
21 21 $ hg status # show changes between repo and working dir
22 22 $ hg diff # generate a unidiff
23 $ hg export # export a changeset as a diff
24 23 $ hg addremove # add all unknown files and remove all missing files
25 24 $ hg commit # commit all changes, edit changelog entry
25 $ hg export # export a changeset as a diff
26 26
27 27 Mercurial will look for a file named .hgignore in the root of your
28 28 repository contains a set of regular expressions to ignore in file
@@ -33,13 +33,14 b' Mercurial commands:'
33 33 $ hg history # show changesets
34 34 $ hg log Makefile # show commits per file
35 35 $ hg checkout # check out the tip revision
36 $ hg checkout <hash> # check out a specified changeset
36 $ hg checkout <id> # check out a specified changeset
37 # IDs can be tags, revision numbers, or unique
38 # subsets of changeset hash numbers
37 39 $ hg add foo # add a new file for the next commit
38 40 $ hg remove bar # mark a file as removed
39 41 $ hg verify # check repo integrity
40 42 $ hg tags # show current tags
41 43 $ hg annotate [files] # show changeset numbers for each file line
42 $ hg blame [files] # show commit users for each file line
43 44
44 45 Branching and merging:
45 46
@@ -69,34 +70,19 b' Importing patches:'
69 70
70 71 Network support:
71 72
72 The simple way:
73
74 73 # pull the self-hosting hg repo
75 74 foo$ hg init
76 75 foo$ hg merge http://selenic.com/hg/
77 76 foo$ hg checkout # hg co works too
78 77
79 # export your .hg directory as a directory on your webserver
80 foo$ ln -s .hg ~/public_html/hg-linux
81
78 # export your current repo via HTTP with browsable interface
79 foo$ hg serve -n "My repo" -p 80
80
82 81 # merge changes from a remote machine
83 bar$ hg merge http://foo/~user/hg-linux
84
85 The new, fast, experimental way:
82 bar$ hg merge hg://foo/
83 bar$ hg co # checkout the result
86 84
87 # pull the self-hosting hg repo
88 foo$ hg init
89 foo$ hg merge hg://selenic.com/hg/
90 foo$ hg checkout # hg co works too
85 # Set up a CGI server on your webserver
86 foo$ cp hgweb.cgi ~/public_html/hg-linux/index.cgi
87 foo$ emacs ~/public_html/hg-linux/index.cgi # adjust the defaults
91 88
92 # Set up the CGI server on your webserver
93 foo$ ln -s .hg ~/public_html/hg-linux/.hg
94 foo$ cp hgweb.py ~/public_html/hg-linux/index.cgi
95
96 # merge changes from a remote machine
97 bar$ hg merge hg://foo/~user/hg-linux
98
99 Another approach which does perform well right now is to use rsync.
100 Simply rsync the remote repo to a read-only local copy and then do a
101 local pull.
102
General Comments 0
You need to be logged in to leave comments. Login now