Fossil

Artifact Content
Login

Artifact ef6f80a6432d6b9825112fad72a7ad4301a7a9c8:

Wiki page [Tutorial] by anonymous 2010-07-25 10:49:57.
D 2010-07-25T10:49:57
L Tutorial
P 59e243b7e9b98bd6734db12c886be6c3d18359f5
U anonymous
W 3038
<h1>Fossil Tutorial</h1>

<i>Note: At this point this is only an outline, not the real thing.  We need to establish what goes into a decent Fossil tutorial before we start writing details.  Initially we may want to append the tutorial pieces so they're clearly labelled and up for discussion.  Once the pieces are in something resembling stable condition, the whole page can be edited and the final form moved up into the tutorial proper.</i>

Outline:
  *  What is Fossil? ([http://www.hwaci.com/cgi-bin/fossil/doc/tip/www/index.wiki|ref])
  *  What distinguishes it from other SCM systems?
  *  How do I get it? ([http://www.fossil-scm.org/fossil/timeline|ref], [http://www.hwaci.com/cgi-bin/fossil/timeline|ref], [http://www.fossil-scm.org/download.html|ref])
  *  How do I build it myself?  ([http://www.hwaci.com/cgi-bin/fossil/doc/tip/www/build.wiki|ref])
  *  What are the common use patterns? ([http://www.hwaci.com/cgi-bin/fossil/doc/tip/www/quickstart.wiki|ref])
  *  Coming to Fossil from CVS.
  *  Coming to Fossil from Subversion.
  *  Coming to Fossil from bzr.
  *  [#fromdarcs|Coming to Fossil from Darcs.]
  *  Coming to Fossil from Mercurial.
  *  Coming to Fossil from git.
  *  Coming to Fossil from ... (what else?).

<hr>


<hr><i>On 2008-05-25 06:41:52 UTC michael added:</i><br />
<h2 id="fromdarcs">Coming to <cite>Fossil</cite> from <cite>darcs</cite></h2>
If you're coming to <cite>Fossil</cite> from <cite>[http://www.darcs.net/|darcs]</cite>, most of <cite>Fossil</cite>'s concepts will not be new to you.  A brief comparison of the two systems will help get you oriented.
<nowiki>
<table width="50%" rules="all" border="1">
 <tr>
  <td><strong>Task</strong></td>
  <td><strong>darcs</strong></td>
  <td><strong>Fossil</strong></td>
 </tr>
 <tr valign="top">
  <td>Create a new repository.</td>
  <td><code>darcs init</code></td>
  <td><code>fossil new repo.fsl</code><sup>1</sup><code><br>fossil open repo.fsl</td>
 <tr valign="top">
  <td>Clone an existing repository.</td>
  <td><code>darcs get {PATH|URL}</code><sup>2</sup></td>
  <td><code>fossil clone URL clone.fsl</code><sup>1</sup><code><br>fossil open clone.fsl</td>
 </tr>
 <tr valign="top">
  <td>Collect changes from a remote repository.</td>
  <td><code>darcs pull [{PATH|URL}]</code></td>
  <td><code>fossil pull [URL]</code></td>
 </tr>
 <tr valign="top">
  <td>Send changes to remote repository.</td>
  <td><code>darcs push [{PATH|URL}]</code></td>
  <td><code>fossil push [URL]</code></td>
 </tr>
</table>
</nowiki>
<sup>1</sup> A <cite>darcs</cite> repository is typically, in its most common use case, a subdirectory of the project directory.  A <cite>Fossil</cite> repository is a single file which can be placed anywhere on your disk.  It does not necessarily (and indeed usually shouldn't) reside in the same place you do your work.

<sup>2</sup> An alternative to using <code>darcs get</code> in the destination repository is to use <code>darcs put</code> in the source repository.
Z 9f5c86b1b0167defd0a20d4d0553e1f8