a9dcbf3ede 2008-12-16    kejoki: <h2>sync</h2>
a9dcbf3ede 2008-12-16    kejoki: 
a9dcbf3ede 2008-12-16    kejoki: The <code>sync</code> command [./cmd_pull.wiki | <code>pull</code>]s and
a9dcbf3ede 2008-12-16    kejoki: [./cmd_push.wiki | <code>push</code>]es repository changes simultaneously.
a9dcbf3ede 2008-12-16    kejoki: 
a9dcbf3ede 2008-12-16    kejoki: This applies to repositories available via a URL, of course.  If your
a9dcbf3ede 2008-12-16    kejoki: project is strictly local you can do all of the distributed stuff as
a9dcbf3ede 2008-12-16    kejoki: long as you are "serving" the repository via http in some fashion, but
a9dcbf3ede 2008-12-16    kejoki: it's probably pointless to do so.
a9dcbf3ede 2008-12-16    kejoki: 
a9dcbf3ede 2008-12-16    kejoki: Assuming you aren't running <b>fossil</b> as a high-powered version of
a9dcbf3ede 2008-12-16    kejoki: [http://www.gnu.org/software/rcs | RCS], your use of <code>sync</code>
a9dcbf3ede 2008-12-16    kejoki: in your projects is up to you.  <b>fossil</b> defaults to using a
a9dcbf3ede 2008-12-16    kejoki: [./cmd_setting.wiki | setting] of <code>autosync</code>
a9dcbf3ede 2008-12-16    kejoki: If you have cloned a repository you will automatically sync with the
a9dcbf3ede 2008-12-16    kejoki: original if you [./cmd_commit.wiki | commit] changes to your local
a9dcbf3ede 2008-12-16    kejoki: version <em>unless</em> you customize your configuration.
a9dcbf3ede 2008-12-16    kejoki: 
a9dcbf3ede 2008-12-16    kejoki: See also: [./cmd_pull.wiki | fossil pull],
a9dcbf3ede 2008-12-16    kejoki: [./cmd_push.wiki | fossil push],
a9dcbf3ede 2008-12-16    kejoki: [./cmd_setting.wiki | fossil setting],
51868cb12f 2009-01-30    kejoki: [./branching.wiki | <i>branching, merging, forking and tagging</i>],
a9dcbf3ede 2008-12-16    kejoki: [./reference.wiki | Reference]