![]() ![]() ![]() The repository can now be browsed with a normal webbrowser at theĪddress There you can see the project historyĪnd the changeset graph, you can examine individual changesets, youĬan see lists of tags and branches, you can annotate files, and youĬan retrieve any revision as a tarball or a zip-file. We will let Alice serve her clone of the hello repository: alice$ hg serve listening at (bound to 127.0.0.1:8000) Or even for browsing the history yourself. This to quickly share a repository with another machine on your LAN, Not have write access to this particular repository.Īs mentioned earlier, Mercurial has a built-in webserver. She won’t be able to push her changeset to the server since she does SheĬan compare her clone with the remote server: alice$ hg outgoing comparing with searching for changes changeset: 1:61c1daa1d929 tag: tip user: Alice date: Sat Jan 22 10:00:00 2011 +0000 summary: Add comma Her own independent copy of the repository and work on it locally. This is the essence of distributed revision control - Alice can get What makes it feasible to create as many local throw-away clones asĪlice can now make her own commits in her clone: alice$ cd hello alice$ echo "Hello, World!" > hello.txt alice$ hg commit -m "Add comma" ![]() It is only the working copies that take up new disk space. Will thus share the disk space used by the two. hg directory by using hardlinks between the files. This is not just due to theįact that reading data over the network is slower than reading it fromĪ disk, but also because a local clone will re-use the space in the Under the covers, Mercurial is able to make the local clone much moreĮfficient than a clone made over HTTP. Repository using a filesystem path: in both cases, Alice ends up withĪ complete copy of the repository and the default branch is We will start by letting Alice clone a small example repository: alice$ hg clone destination directory: hello requesting all changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files updating to branch default 1 files updated, 0 files merged, 0 files removed, 0 files unresolvedĪs you can see, this is not relly different from when Alice cloned a Login shell, see the hg-ssh script for details. Users can only execute Mercurial-related commands do not get a full Possible to setup an account with a restricted login shell so that Then using SSH is the easiest way to clone a repository. If you already have SSH login on a server with Mercurial installed, ![]() SSH: the secure shell protocol used on many Unix systems. With hg serve and which will let you browse the repository history Mercurial comes with a small built-in webserver that you can start HTTP: the protocol used by normal webservers. Is why Mercurial can access remote repositories over a network Users don’t have direct access to each other’s files like that. Setup when Alice and Bob share a filesystem between them, but most In the Basic Mercurial guide, you saw how Alice and Bob could pushĪnd pull between each other on the same filesystem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |