comparison en/ch01-tour-basic.xml @ 826:a17d6390a480

More fixes to chapters 1 and 2.

825:d7d09cda83d2

      <para id="x_61">If you look back at the output of <command
	  role="hg-cmd">hg pull</command> in <xref
	    linkend="sec:tour:pull"/> when we ran it without <option
	  role="hg-opt-pull">-u</option>, you can see that it printed
	a helpful reminder that we'd have to take an explicit step to
	update the working directory:</para>

      <!-- &interaction.xxx.fixme; -->

      <para id="x_62">To find out what revision the working directory
	is at, use the <command role="hg-cmd">hg parents</command>
	command.</para>

	it.</para>

      &interaction.tour.push.net;
    </sect2>
  </sect1>
</chapter>

<!--
local variables: 
sgml-parent-document: ("00book.xml" "book" "chapter")

826:a17d6390a480

      <para id="x_61">If you look back at the output of <command
	  role="hg-cmd">hg pull</command> in <xref
	    linkend="sec:tour:pull"/> when we ran it without <option
	  role="hg-opt-pull">-u</option>, you can see that it printed
	a helpful reminder that we'd have to take an explicit step to
	update the working directory.</para>

      <para id="x_62">To find out what revision the working directory
	is at, use the <command role="hg-cmd">hg parents</command>
	command.</para>

	it.</para>

      &interaction.tour.push.net;
    </sect2>
  </sect1>

  <sect1>
    <title>Starting a new project</title>

    <para>It is just as easy to begin a new project as to work on one
      that already exists.  The <command>hg init</command> command
      creates a new, empty Mercurial repository.</para>

    &interaction.ch01-new.init;

    <para>This simply creates a repository named
      <filename>myproject</filename> in the current directory.</para>

    &interaction.ch01-new.ls;

    <para>We can tell that <filename>myproject</filename> is a
      Mercurial repository, because it contains a
      <filename>.hg</filename> directory.</para>

    &interaction.ch01-new.ls2;

    <para>If we want to add some pre-existing files to the repository,
      we copy them into place, and tell Mercurial to start tracking
      them using the <command>hg add</command> command.</para>

    &interaction.ch01-new.add;

    <para>Once we are satisfied that our project looks right, we
      commit our changes.</para>

    &interaction.ch01-new.commit;

    <para>It takes just a few moments to start using Mercurial on a
      new project, which is part of its appeal. Revision control is
      now so easy to work with, we can use it on the smallest of
      projects that we might not have considered with a more
      complicated tool.</para>
  </sect1>
</chapter>

<!--
local variables: 
sgml-parent-document: ("00book.xml" "book" "chapter")