hgbook
view en/tour-basic.tex @ 317:cd595464fea9
Added a source for Solaris Mercurial binaries
| author | Sean Russell <ser@ser1.net> |
|---|---|
| date | Thu Aug 21 23:26:38 2008 -0400 (2008-08-21) |
| parents | f8a2fe77908d |
| children | 1d277d6aa187 |
line source
1 \chapter{A tour of Mercurial: the basics}
2 \label{chap:tour-basic}
4 \section{Installing Mercurial on your system}
5 \label{sec:tour:install}
7 Prebuilt binary packages of Mercurial are available for every popular
8 operating system. These make it easy to start using Mercurial on your
9 computer immediately.
11 \subsection{Linux}
13 Because each Linux distribution has its own packaging tools, policies,
14 and rate of development, it's difficult to give a comprehensive set of
15 instructions on how to install Mercurial binaries. The version of
16 Mercurial that you will end up with can vary depending on how active
17 the person is who maintains the package for your distribution.
19 To keep things simple, I will focus on installing Mercurial from the
20 command line under the most popular Linux distributions. Most of
21 these distributions provide graphical package managers that will let
22 you install Mercurial with a single click; the package name to look
23 for is \texttt{mercurial}.
25 \begin{itemize}
26 \item[Debian]
27 \begin{codesample4}
28 apt-get install mercurial
29 \end{codesample4}
31 \item[Fedora Core]
32 \begin{codesample4}
33 yum install mercurial
34 \end{codesample4}
36 \item[Gentoo]
37 \begin{codesample4}
38 emerge mercurial
39 \end{codesample4}
41 \item[OpenSUSE]
42 \begin{codesample4}
43 yum install mercurial
44 \end{codesample4}
46 \item[Ubuntu] Ubuntu's Mercurial package is based on Debian's. To
47 install it, run the following command.
48 \begin{codesample4}
49 apt-get install mercurial
50 \end{codesample4}
51 The Ubuntu package for Mercurial tends to lag behind the Debian
52 version by a considerable time margin (at the time of writing, seven
53 months), which in some cases will mean that on Ubuntu, you may run
54 into problems that have since been fixed in the Debian package.
55 \end{itemize}
57 \subsection{Solaris}
59 SunFreeWare, at \url{http://www.sunfreeware.com}, is a good source for a
60 large number of pre-built Solaris packages for 32 and 64 bit Intel and
61 Sparc architectures, including current versions of Mercurial.
63 \subsection{Mac OS X}
65 Lee Cantey publishes an installer of Mercurial for Mac OS~X at
66 \url{http://mercurial.berkwood.com}. This package works on both
67 Intel-~and Power-based Macs. Before you can use it, you must install
68 a compatible version of Universal MacPython~\cite{web:macpython}. This
69 is easy to do; simply follow the instructions on Lee's site.
71 \subsection{Windows}
73 Lee Cantey also publishes an installer of Mercurial for Windows at
74 \url{http://mercurial.berkwood.com}. This package has no external
75 dependencies; it ``just works''.
77 \begin{note}
78 The Windows version of Mercurial does not automatically convert line
79 endings between Windows and Unix styles. If you want to share work
80 with Unix users, you must do a little additional configuration
81 work. XXX Flesh this out.
82 \end{note}
84 \section{Getting started}
86 To begin, we'll use the \hgcmd{version} command to find out whether
87 Mercurial is actually installed properly. The actual version
88 information that it prints isn't so important; it's whether it prints
89 anything at all that we care about.
90 \interaction{tour.version}
92 \subsection{Built-in help}
94 Mercurial provides a built-in help system. This is invaluable for those
95 times when you find yourself stuck trying to remember how to run a
96 command. If you are completely stuck, simply run \hgcmd{help}; it
97 will print a brief list of commands, along with a description of what
98 each does. If you ask for help on a specific command (as below), it
99 prints more detailed information.
100 \interaction{tour.help}
101 For a more impressive level of detail (which you won't usually need)
102 run \hgcmdargs{help}{\hggopt{-v}}. The \hggopt{-v} option is short
103 for \hggopt{--verbose}, and tells Mercurial to print more information
104 than it usually would.
106 \section{Working with a repository}
108 In Mercurial, everything happens inside a \emph{repository}. The
109 repository for a project contains all of the files that ``belong to''
110 that project, along with a historical record of the project's files.
112 There's nothing particularly magical about a repository; it is simply
113 a directory tree in your filesystem that Mercurial treats as special.
114 You can rename or delete a repository any time you like, using either the
115 command line or your file browser.
117 \subsection{Making a local copy of a repository}
119 \emph{Copying} a repository is just a little bit special. While you
120 could use a normal file copying command to make a copy of a
121 repository, it's best to use a built-in command that Mercurial
122 provides. This command is called \hgcmd{clone}, because it creates an
123 identical copy of an existing repository.
124 \interaction{tour.clone}
125 If our clone succeeded, we should now have a local directory called
126 \dirname{hello}. This directory will contain some files.
127 \interaction{tour.ls}
128 These files have the same contents and history in our repository as
129 they do in the repository we cloned.
131 Every Mercurial repository is complete, self-contained, and
132 independent. It contains its own private copy of a project's files
133 and history. A cloned repository remembers the location of the
134 repository it was cloned from, but it does not communicate with that
135 repository, or any other, unless you tell it to.
137 What this means for now is that we're free to experiment with our
138 repository, safe in the knowledge that it's a private ``sandbox'' that
139 won't affect anyone else.
141 \subsection{What's in a repository?}
143 When we take a more detailed look inside a repository, we can see that
144 it contains a directory named \dirname{.hg}. This is where Mercurial
145 keeps all of its metadata for the repository.
146 \interaction{tour.ls-a}
148 The contents of the \dirname{.hg} directory and its subdirectories are
149 private to Mercurial. Every other file and directory in the
150 repository is yours to do with as you please.
152 To introduce a little terminology, the \dirname{.hg} directory is the
153 ``real'' repository, and all of the files and directories that coexist
154 with it are said to live in the \emph{working directory}. An easy way
155 to remember the distinction is that the \emph{repository} contains the
156 \emph{history} of your project, while the \emph{working directory}
157 contains a \emph{snapshot} of your project at a particular point in
158 history.
160 \section{A tour through history}
162 One of the first things we might want to do with a new, unfamiliar
163 repository is understand its history. The \hgcmd{log} command gives
164 us a view of history.
165 \interaction{tour.log}
166 By default, this command prints a brief paragraph of output for each
167 change to the project that was recorded. In Mercurial terminology, we
168 call each of these recorded events a \emph{changeset}, because it can
169 contain a record of changes to several files.
171 The fields in a record of output from \hgcmd{log} are as follows.
172 \begin{itemize}
173 \item[\texttt{changeset}] This field has the format of a number,
174 followed by a colon, followed by a hexadecimal string. These are
175 \emph{identifiers} for the changeset. There are two identifiers
176 because the number is shorter and easier to type than the hex
177 string.
178 \item[\texttt{user}] The identity of the person who created the
179 changeset. This is a free-form field, but it most often contains a
180 person's name and email address.
181 \item[\texttt{date}] The date and time on which the changeset was
182 created, and the timezone in which it was created. (The date and
183 time are local to that timezone; they display what time and date it
184 was for the person who created the changeset.)
185 \item[\texttt{summary}] The first line of the text message that the
186 creator of the changeset entered to describe the changeset.
187 \end{itemize}
188 The default output printed by \hgcmd{log} is purely a summary; it is
189 missing a lot of detail.
191 Figure~\ref{fig:tour-basic:history} provides a graphical representation of
192 the history of the \dirname{hello} repository, to make it a little
193 easier to see which direction history is ``flowing'' in. We'll be
194 returning to this figure several times in this chapter and the chapter
195 that follows.
197 \begin{figure}[ht]
198 \centering
199 \grafix{tour-history}
200 \caption{Graphical history of the \dirname{hello} repository}
201 \label{fig:tour-basic:history}
202 \end{figure}
204 \subsection{Changesets, revisions, and talking to other
205 people}
207 As English is a notoriously sloppy language, and computer science has
208 a hallowed history of terminological confusion (why use one term when
209 four will do?), revision control has a variety of words and phrases
210 that mean the same thing. If you are talking about Mercurial history
211 with other people, you will find that the word ``changeset'' is often
212 compressed to ``change'' or (when written) ``cset'', and sometimes a
213 changeset is referred to as a ``revision'' or a ``rev''.
215 While it doesn't matter what \emph{word} you use to refer to the
216 concept of ``a~changeset'', the \emph{identifier} that you use to
217 refer to ``a~\emph{specific} changeset'' is of great importance.
218 Recall that the \texttt{changeset} field in the output from
219 \hgcmd{log} identifies a changeset using both a number and a
220 hexadecimal string.
221 \begin{itemize}
222 \item The revision number is \emph{only valid in that repository},
223 \item while the hex string is the \emph{permanent, unchanging
224 identifier} that will always identify that exact changeset in
225 \emph{every} copy of the repository.
226 \end{itemize}
227 This distinction is important. If you send someone an email talking
228 about ``revision~33'', there's a high likelihood that their
229 revision~33 will \emph{not be the same} as yours. The reason for this
230 is that a revision number depends on the order in which changes
231 arrived in a repository, and there is no guarantee that the same
232 changes will happen in the same order in different repositories.
233 Three changes $a,b,c$ can easily appear in one repository as $0,1,2$,
234 while in another as $1,0,2$.
236 Mercurial uses revision numbers purely as a convenient shorthand. If
237 you need to discuss a changeset with someone, or make a record of a
238 changeset for some other reason (for example, in a bug report), use
239 the hexadecimal identifier.
241 \subsection{Viewing specific revisions}
243 To narrow the output of \hgcmd{log} down to a single revision, use the
244 \hgopt{log}{-r} (or \hgopt{log}{--rev}) option. You can use either a
245 revision number or a long-form changeset identifier, and you can
246 provide as many revisions as you want. \interaction{tour.log-r}
248 If you want to see the history of several revisions without having to
249 list each one, you can use \emph{range notation}; this lets you
250 express the idea ``I want all revisions between $a$ and $b$,
251 inclusive''.
252 \interaction{tour.log.range}
253 Mercurial also honours the order in which you specify revisions, so
254 \hgcmdargs{log}{-r 2:4} prints $2,3,4$ while \hgcmdargs{log}{-r 4:2}
255 prints $4,3,2$.
257 \subsection{More detailed information}
259 While the summary information printed by \hgcmd{log} is useful if you
260 already know what you're looking for, you may need to see a complete
261 description of the change, or a list of the files changed, if you're
262 trying to decide whether a changeset is the one you're looking for.
263 The \hgcmd{log} command's \hggopt{-v} (or \hggopt{--verbose})
264 option gives you this extra detail.
265 \interaction{tour.log-v}
267 If you want to see both the description and content of a change, add
268 the \hgopt{log}{-p} (or \hgopt{log}{--patch}) option. This displays
269 the content of a change as a \emph{unified diff} (if you've never seen
270 a unified diff before, see section~\ref{sec:mq:patch} for an overview).
271 \interaction{tour.log-vp}
273 \section{All about command options}
275 Let's take a brief break from exploring Mercurial commands to discuss
276 a pattern in the way that they work; you may find this useful to keep
277 in mind as we continue our tour.
279 Mercurial has a consistent and straightforward approach to dealing
280 with the options that you can pass to commands. It follows the
281 conventions for options that are common to modern Linux and Unix
282 systems.
283 \begin{itemize}
284 \item Every option has a long name. For example, as we've already
285 seen, the \hgcmd{log} command accepts a \hgopt{log}{--rev} option.
286 \item Most options have short names, too. Instead of
287 \hgopt{log}{--rev}, we can use \hgopt{log}{-r}. (The reason that
288 some options don't have short names is that the options in question
289 are rarely used.)
290 \item Long options start with two dashes (e.g.~\hgopt{log}{--rev}),
291 while short options start with one (e.g.~\hgopt{log}{-r}).
292 \item Option naming and usage is consistent across commands. For
293 example, every command that lets you specify a changeset~ID or
294 revision number accepts both \hgopt{log}{-r} and \hgopt{log}{--rev}
295 arguments.
296 \end{itemize}
297 In the examples throughout this book, I use short options instead of
298 long. This just reflects my own preference, so don't read anything
299 significant into it.
301 Most commands that print output of some kind will print more output
302 when passed a \hggopt{-v} (or \hggopt{--verbose}) option, and less
303 when passed \hggopt{-q} (or \hggopt{--quiet}).
305 \section{Making and reviewing changes}
307 Now that we have a grasp of viewing history in Mercurial, let's take a
308 look at making some changes and examining them.
310 The first thing we'll do is isolate our experiment in a repository of
311 its own. We use the \hgcmd{clone} command, but we don't need to
312 clone a copy of the remote repository. Since we already have a copy
313 of it locally, we can just clone that instead. This is much faster
314 than cloning over the network, and cloning a local repository uses
315 less disk space in most cases, too.
316 \interaction{tour.reclone}
317 As an aside, it's often good practice to keep a ``pristine'' copy of a
318 remote repository around, which you can then make temporary clones of
319 to create sandboxes for each task you want to work on. This lets you
320 work on multiple tasks in parallel, each isolated from the others
321 until it's complete and you're ready to integrate it back. Because
322 local clones are so cheap, there's almost no overhead to cloning and
323 destroying repositories whenever you want.
325 In our \dirname{my-hello} repository, we have a file
326 \filename{hello.c} that contains the classic ``hello, world'' program.
327 Let's use the ancient and venerable \command{sed} command to edit this
328 file so that it prints a second line of output. (I'm only using
329 \command{sed} to do this because it's easy to write a scripted example
330 this way. Since you're not under the same constraint, you probably
331 won't want to use \command{sed}; simply use your preferred text editor to
332 do the same thing.)
333 \interaction{tour.sed}
335 Mercurial's \hgcmd{status} command will tell us what Mercurial knows
336 about the files in the repository.
337 \interaction{tour.status}
338 The \hgcmd{status} command prints no output for some files, but a line
339 starting with ``\texttt{M}'' for \filename{hello.c}. Unless you tell
340 it to, \hgcmd{status} will not print any output for files that have
341 not been modified.
343 The ``\texttt{M}'' indicates that Mercurial has noticed that we
344 modified \filename{hello.c}. We didn't need to \emph{inform}
345 Mercurial that we were going to modify the file before we started, or
346 that we had modified the file after we were done; it was able to
347 figure this out itself.
349 It's a little bit helpful to know that we've modified
350 \filename{hello.c}, but we might prefer to know exactly \emph{what}
351 changes we've made to it. To do this, we use the \hgcmd{diff}
352 command.
353 \interaction{tour.diff}
355 \section{Recording changes in a new changeset}
357 We can modify files, build and test our changes, and use
358 \hgcmd{status} and \hgcmd{diff} to review our changes, until we're
359 satisfied with what we've done and arrive at a natural stopping point
360 where we want to record our work in a new changeset.
362 The \hgcmd{commit} command lets us create a new changeset; we'll
363 usually refer to this as ``making a commit'' or ``committing''.
365 \subsection{Setting up a username}
367 When you try to run \hgcmd{commit} for the first time, it is not
368 guaranteed to succeed. Mercurial records your name and address with
369 each change that you commit, so that you and others will later be able
370 to tell who made each change. Mercurial tries to automatically figure
371 out a sensible username to commit the change with. It will attempt
372 each of the following methods, in order:
373 \begin{enumerate}
374 \item If you specify a \hgopt{commit}{-u} option to the \hgcmd{commit}
375 command on the command line, followed by a username, this is always
376 given the highest precedence.
377 \item If you have set the \envar{HGUSER} environment variable, this is
378 checked next.
379 \item If you create a file in your home directory called
380 \sfilename{.hgrc}, with a \rcitem{ui}{username} entry, that will be
381 used next. To see what the contents of this file should look like,
382 refer to section~\ref{sec:tour-basic:username} below.
383 \item If you have set the \envar{EMAIL} environment variable, this
384 will be used next.
385 \item Mercurial will query your system to find out your local user
386 name and host name, and construct a username from these components.
387 Since this often results in a username that is not very useful, it
388 will print a warning if it has to do this.
389 \end{enumerate}
390 If all of these mechanisms fail, Mercurial will fail, printing an
391 error message. In this case, it will not let you commit until you set
392 up a username.
394 You should think of the \envar{HGUSER} environment variable and the
395 \hgopt{commit}{-u} option to the \hgcmd{commit} command as ways to
396 \emph{override} Mercurial's default selection of username. For normal
397 use, the simplest and most robust way to set a username for yourself
398 is by creating a \sfilename{.hgrc} file; see below for details.
400 \subsubsection{Creating a Mercurial configuration file}
401 \label{sec:tour-basic:username}
403 To set a user name, use your favourite editor to create a file called
404 \sfilename{.hgrc} in your home directory. Mercurial will use this
405 file to look up your personalised configuration settings. The initial
406 contents of your \sfilename{.hgrc} should look like this.
407 \begin{codesample2}
408 # This is a Mercurial configuration file.
409 [ui]
410 username = Firstname Lastname <email.address@domain.net>
411 \end{codesample2}
412 The ``\texttt{[ui]}'' line begins a \emph{section} of the config file,
413 so you can read the ``\texttt{username = ...}'' line as meaning ``set
414 the value of the \texttt{username} item in the \texttt{ui} section''.
415 A section continues until a new section begins, or the end of the
416 file. Mercurial ignores empty lines and treats any text from
417 ``\texttt{\#}'' to the end of a line as a comment.
419 \subsubsection{Choosing a user name}
421 You can use any text you like as the value of the \texttt{username}
422 config item, since this information is for reading by other people,
423 but for interpreting by Mercurial. The convention that most people
424 follow is to use their name and email address, as in the example
425 above.
427 \begin{note}
428 Mercurial's built-in web server obfuscates email addresses, to make
429 it more difficult for the email harvesting tools that spammers use.
430 This reduces the likelihood that you'll start receiving more junk
431 email if you publish a Mercurial repository on the web.
432 \end{note}
434 \subsection{Writing a commit message}
436 When we commit a change, Mercurial drops us into a text editor, to
437 enter a message that will describe the modifications we've made in
438 this changeset. This is called the \emph{commit message}. It will be
439 a record for readers of what we did and why, and it will be printed by
440 \hgcmd{log} after we've finished committing.
441 \interaction{tour.commit}
443 The editor that the \hgcmd{commit} command drops us into will contain
444 an empty line, followed by a number of lines starting with
445 ``\texttt{HG:}''.
446 \begin{codesample2}
447 \emph{empty line}
448 HG: changed hello.c
449 \end{codesample2}
450 Mercurial ignores the lines that start with ``\texttt{HG:}''; it uses
451 them only to tell us which files it's recording changes to. Modifying
452 or deleting these lines has no effect.
454 \subsection{Writing a good commit message}
456 Since \hgcmd{log} only prints the first line of a commit message by
457 default, it's best to write a commit message whose first line stands
458 alone. Here's a real example of a commit message that \emph{doesn't}
459 follow this guideline, and hence has a summary that is not readable.
460 \begin{codesample2}
461 changeset: 73:584af0e231be
462 user: Censored Person <censored.person@example.org>
463 date: Tue Sep 26 21:37:07 2006 -0700
464 summary: include buildmeister/commondefs. Add an exports and install
465 \end{codesample2}
467 As far as the remainder of the contents of the commit message are
468 concerned, there are no hard-and-fast rules. Mercurial itself doesn't
469 interpret or care about the contents of the commit message, though
470 your project may have policies that dictate a certain kind of
471 formatting.
473 My personal preference is for short, but informative, commit messages
474 that tell me something that I can't figure out with a quick glance at
475 the output of \hgcmdargs{log}{--patch}.
477 \subsection{Aborting a commit}
479 If you decide that you don't want to commit while in the middle of
480 editing a commit message, simply exit from your editor without saving
481 the file that it's editing. This will cause nothing to happen to
482 either the repository or the working directory.
484 If we run the \hgcmd{commit} command without any arguments, it records
485 all of the changes we've made, as reported by \hgcmd{status} and
486 \hgcmd{diff}.
488 \subsection{Admiring our new handiwork}
490 Once we've finished the commit, we can use the \hgcmd{tip} command to
491 display the changeset we just created. This command produces output
492 that is identical to \hgcmd{log}, but it only displays the newest
493 revision in the repository.
494 \interaction{tour.tip}
495 We refer to the newest revision in the repository as the tip revision,
496 or simply the tip.
498 \section{Sharing changes}
500 We mentioned earlier that repositories in Mercurial are
501 self-contained. This means that the changeset we just created exists
502 only in our \dirname{my-hello} repository. Let's look at a few ways
503 that we can propagate this change into other repositories.
505 \subsection{Pulling changes from another repository}
506 \label{sec:tour:pull}
508 To get started, let's clone our original \dirname{hello} repository,
509 which does not contain the change we just committed. We'll call our
510 temporary repository \dirname{hello-pull}.
511 \interaction{tour.clone-pull}
513 We'll use the \hgcmd{pull} command to bring changes from
514 \dirname{my-hello} into \dirname{hello-pull}. However, blindly
515 pulling unknown changes into a repository is a somewhat scary
516 prospect. Mercurial provides the \hgcmd{incoming} command to tell us
517 what changes the \hgcmd{pull} command \emph{would} pull into the
518 repository, without actually pulling the changes in.
519 \interaction{tour.incoming}
520 (Of course, someone could cause more changesets to appear in the
521 repository that we ran \hgcmd{incoming} in, before we get a chance to
522 \hgcmd{pull} the changes, so that we could end up pulling changes that we
523 didn't expect.)
525 Bringing changes into a repository is a simple matter of running the
526 \hgcmd{pull} command, and telling it which repository to pull from.
527 \interaction{tour.pull}
528 As you can see from the before-and-after output of \hgcmd{tip}, we
529 have successfully pulled changes into our repository. There remains
530 one step before we can see these changes in the working directory.
532 \subsection{Updating the working directory}
534 We have so far glossed over the relationship between a repository and
535 its working directory. The \hgcmd{pull} command that we ran in
536 section~\ref{sec:tour:pull} brought changes into the repository, but
537 if we check, there's no sign of those changes in the working
538 directory. This is because \hgcmd{pull} does not (by default) touch
539 the working directory. Instead, we use the \hgcmd{update} command to
540 do this.
541 \interaction{tour.update}
543 It might seem a bit strange that \hgcmd{pull} doesn't update the
544 working directory automatically. There's actually a good reason for
545 this: you can use \hgcmd{update} to update the working directory to
546 the state it was in at \emph{any revision} in the history of the
547 repository. If you had the working directory updated to an old
548 revision---to hunt down the origin of a bug, say---and ran a
549 \hgcmd{pull} which automatically updated the working directory to a
550 new revision, you might not be terribly happy.
552 However, since pull-then-update is such a common thing to do,
553 Mercurial lets you combine the two by passing the \hgopt{pull}{-u}
554 option to \hgcmd{pull}.
555 \begin{codesample2}
556 hg pull -u
557 \end{codesample2}
558 If you look back at the output of \hgcmd{pull} in
559 section~\ref{sec:tour:pull} when we ran it without \hgopt{pull}{-u},
560 you can see that it printed a helpful reminder that we'd have to take
561 an explicit step to update the working directory:
562 \begin{codesample2}
563 (run 'hg update' to get a working copy)
564 \end{codesample2}
566 To find out what revision the working directory is at, use the
567 \hgcmd{parents} command.
568 \interaction{tour.parents}
569 If you look back at figure~\ref{fig:tour-basic:history}, you'll see
570 arrows connecting each changeset. The node that the arrow leads
571 \emph{from} in each case is a parent, and the node that the arrow
572 leads \emph{to} is its child. The working directory has a parent in
573 just the same way; this is the changeset that the working directory
574 currently contains.
576 To update the working directory to a particular revision, give a
577 revision number or changeset~ID to the \hgcmd{update} command.
578 \interaction{tour.older}
579 If you omit an explicit revision, \hgcmd{update} will update to the
580 tip revision, as shown by the second call to \hgcmd{update} in the
581 example above.
583 \subsection{Pushing changes to another repository}
585 Mercurial lets us push changes to another repository, from the
586 repository we're currently visiting. As with the example of
587 \hgcmd{pull} above, we'll create a temporary repository to push our
588 changes into.
589 \interaction{tour.clone-push}
590 The \hgcmd{outgoing} command tells us what changes would be pushed
591 into another repository.
592 \interaction{tour.outgoing}
593 And the \hgcmd{push} command does the actual push.
594 \interaction{tour.push}
595 As with \hgcmd{pull}, the \hgcmd{push} command does not update the
596 working directory in the repository that it's pushing changes into.
597 (Unlike \hgcmd{pull}, \hgcmd{push} does not provide a \texttt{-u}
598 option that updates the other repository's working directory.)
600 What happens if we try to pull or push changes and the receiving
601 repository already has those changes? Nothing too exciting.
602 \interaction{tour.push.nothing}
604 \subsection{Sharing changes over a network}
606 The commands we have covered in the previous few sections are not
607 limited to working with local repositories. Each works in exactly the
608 same fashion over a network connection; simply pass in a URL instead
609 of a local path.
610 \interaction{tour.outgoing.net}
611 In this example, we can see what changes we could push to the remote
612 repository, but the repository is understandably not set up to let
613 anonymous users push to it.
614 \interaction{tour.push.net}
616 %%% Local Variables:
617 %%% mode: latex
618 %%% TeX-master: "00book"
619 %%% End: