Fossil: Artifact Content

Artifact 89c914e396d6fa1fb5db5b43c794e5d407d64345

File www/cmd_update.wiki part of check-in [51868cb12f] - Changed update docs, ** ADDED A _SPECIAL_ (but MUTYPE_BLOCK) wikitag <annotation> to put html comments in wikimarkup by kkennell on 2009-01-30 21:18:10.

update

Updating a repository is the process of applying to it changes made by external entities. Contrast this with commiting a locally made change; updating is a bit like "committing" external changes to the local repo.

Update merges changes from the repository into your checkout. That means that it won't have any effect unless there are changes in the repository. The only way the checkout can affect the repo (this is the local repo we're talking about) is if you do a ci. So, update only really makes sense if you have pulled changes from the master repository into the local repository.

<annotation> Note : really really need a quick overview of the pull-update-edit-commit-push workflow, and the shortcuts for that, and re-emphasize the role of autosync in changing the basic nature of the workflow </annotation>

Local intranet commits (by someone else) or Net pulls from a server will usually require a fossil update afterward, because they are likely not to be done in autosync mode.

Local commits are likely to be made with automatic syncing set to "on", however, so if you don't use fossil for Net-wide projects you may never have to use update.