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