maintaining.texi 94.7 KB
Newer Older
Glenn Morris's avatar
Glenn Morris committed
1
@c This is part of the Emacs manual.
2
@c Copyright (C) 1985-1987, 1993-1995, 1997, 1999-2011
3
@c   Free Software Foundation, Inc.
Glenn Morris's avatar
Glenn Morris committed
4 5 6 7 8
@c See file emacs.texi for copying conditions.
@node Maintaining, Abbrevs, Building, Top
@chapter Maintaining Large Programs

  This chapter describes Emacs features for maintaining large
9
programs.
Glenn Morris's avatar
Glenn Morris committed
10 11

@menu
12
* Version Control::     Using version control systems.
13 14 15
* Change Log::          Maintaining a change history for your program.
* Tags::                Go directly to any function in your program in one
                          command.  Tags remembers which file it is in.
16
* EDE::                 An integrated development environment for Emacs.
Glenn Morris's avatar
Glenn Morris committed
17 18 19 20 21
@ifnottex
* Emerge::              A convenient way of merging two versions of a program.
@end ifnottex
@end menu

22 23 24 25
@node Version Control
@section Version Control
@cindex version control

26
  A @dfn{version control system} is a program that can record multiple
27
versions of a source file, storing information such as the creation
28 29 30 31 32 33 34 35 36 37 38 39
time of each version, who made it, and a description of what was
changed.

  The Emacs version control interface is called @dfn{VC}.  VC commands
work with several different version control systems; currently, it
supports GNU Arch, Bazaar, CVS, Git, Mercurial, Monotone, RCS,
SCCS/CSSC, and Subversion.  Of these, the GNU project distributes CVS,
Arch, RCS, and Bazaar.

  VC is enabled automatically whenever you visit a file governed by a
version control system.  To disable VC entirely, set the customizable
variable @code{vc-handled-backends} to @code{nil}
40 41 42 43 44 45 46 47 48 49 50
@iftex
(@pxref{Customizing VC,,,emacs-xtra, Specialized Emacs Features}).
@end iftex
@ifnottex
(@pxref{Customizing VC}).
@end ifnottex

@menu
* Introduction to VC::  How version control works in general.
* VC Mode Line::        How the mode line shows version control status.
* Basic VC Editing::    How to edit a file under version control.
51
* Log Buffer::          Features available in log entry buffers.
52
* Registering::         Putting a file under version control.
53
* Old Revisions::       Examining and comparing old versions.
54 55
* VC Change Log::       Viewing the VC Change Log.
* VC Undo::             Canceling changes before or after committing.
56 57 58 59 60 61 62 63 64 65 66 67
* VC Directory Mode::   Listing files managed by version control.
* Branches::            Multiple lines of development.
@ifnottex
* Miscellaneous VC::    Various other commands and features of VC.
* Customizing VC::      Variables that change VC's behavior.
@end ifnottex
@end menu

@node Introduction to VC
@subsection Introduction to Version Control

  VC allows you to use a version control system from within Emacs,
68 69 70 71 72 73
integrating the version control operations smoothly with editing.  It
provides a uniform interface for common operations in many version
control operations.

  Some uncommon or intricate version control operations, such as
altering repository settings, are not supported in VC.  You should
74
perform such tasks outside Emacs, e.g.@: via the command line.
75 76 77 78 79 80 81

  This section provides a general overview of version control, and
describes the version control systems that VC supports.  You can skip
this section if you are already familiar with the version control system
you want to use.

@menu
82
* Why Version Control?::    Understanding the problems it addresses.
83 84
* Version Control Systems:: Supported version control back-end systems.
* VCS Concepts::            Words and concepts related to version control.
85 86 87
* VCS Merging::             How file conflicts are handled.
* VCS Changesets::          How changes are grouped.
* VCS Repositories::        Where version control repositories are stored.
88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118
* Types of Log File::       The VCS log in contrast to the ChangeLog.
@end menu

@node Why Version Control?
@subsubsection Understanding the problems it addresses

  Version control systems provide you with three important
capabilities:

@itemize @bullet
@item
@dfn{Reversibility}: the ability to back up to a previous state if you
discover that some modification you did was a mistake or a bad idea.

@item
@dfn{Concurrency}: the ability to have many people modifying the same
collection of files knowing that conflicting modifications can be
detected and resolved.

@item
@dfn{History}: the ability to attach historical data to your data,
such as explanatory comments about the intention behind each change to
it.  Even for a programmer working solo, change histories are an
important aid to memory; for a multi-person project, they are a
vitally important form of communication among developers.
@end itemize

@node Version Control Systems
@subsubsection Supported Version Control Systems

@cindex back end (version control)
119 120
  VC currently works with many different version control systems,
which it refers to as @dfn{back ends}:
121 122 123 124 125 126 127

@itemize @bullet

@cindex SCCS
@item
SCCS was the first version control system ever built, and was long ago
superseded by more advanced ones.  VC compensates for certain features
128
missing in SCCS (e.g.@: tag names for releases) by implementing them
129 130 131 132 133 134 135 136 137 138 139 140
itself.  Other VC features, such as multiple branches, are simply
unavailable.  Since SCCS is non-free, we recommend avoiding it.

@cindex CSSC
@item
CSSC is a free replacement for SCCS.  You should use CSSC only if, for
some reason, you cannot use a more recent and better-designed version
control system.

@cindex RCS
@item
RCS is the free version control system around which VC was initially
141 142 143
built.  It is relatively primitive: it cannot be used over the
network, and works at the level of individual files.  Almost
everything you can do with RCS can be done through VC.
144 145 146 147 148 149

@cindex CVS
@item
CVS is the free version control system that was, until recently (circa
2008), used by the majority of free software projects.  Nowadays, it
is slowly being superseded by newer systems.  CVS allows concurrent
150 151 152
multi-user development either locally or over the network.  Unlike
newer systems, it lacks support for atomic commits and file
moving/renaming.  VC supports all basic editing operations under CVS.
153 154 155 156

@cindex SVN
@cindex Subversion
@item
157
Subversion (svn) is a free version control system designed to be
158 159 160
similar to CVS but without its problems (e.g., it supports atomic
commits of filesets, and versioning of directories, symbolic links,
meta-data, renames, copies, and deletes).
161 162 163 164

@cindex GNU Arch
@cindex Arch
@item
165
GNU Arch is one of the earliest @dfn{decentralized} version control
166
systems (the other being Monotone).  @xref{VCS Concepts}, for a
167
description of decentralized version control systems.  It is no longer
168
under active development, and has been deprecated in favor of Bazaar.
169 170 171

@cindex git
@item
172
Git is a decentralized version control system originally invented by
173
Linus Torvalds to support development of Linux (his kernel).  VC
174
supports many common Git operations, but others, such as repository
175
syncing, must be done from the command line.
176 177 178 179

@cindex hg
@cindex Mercurial
@item
180
Mercurial (hg) is a decentralized version control system broadly
181
resembling Git.  VC supports most Mercurial commands, with the
182
exception of repository sync operations.
183 184 185 186

@cindex bzr
@cindex Bazaar
@item
187 188
Bazaar (bzr) is a decentralized version control system that supports
both repository-based and decentralized versioning.  VC supports most
189
basic editing operations under Bazaar.
190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205
@end itemize

@node VCS Concepts
@subsubsection Concepts of Version Control

@cindex repository
@cindex registered file
   When a file is under version control, we say that it is
@dfn{registered} in the version control system.  The system has a
@dfn{repository} which stores both the file's present state and its
change history---enough to reconstruct the current version or any
earlier version.  The repository also contains other information, such
as @dfn{log entries} that describe the changes made to each file.

@cindex work file
@cindex checking out files
206 207 208
  The copy of a version-controlled file that you actually edit is
called the @dfn{work file}.  You can change each work file as you
would an ordinary file.  After you are done with a set of changes, you
209 210
may @dfn{commit} (or @dfn{check in}) the changes; this records the
changes in the repository, along with a descriptive log entry.
211

212 213 214
@cindex working tree
  A directory tree of work files is called a @dfn{working tree}.

215 216
@cindex revision
@cindex revision ID
217 218 219 220 221
  Each commit creates a new @dfn{revision} in the repository.  The
version control system keeps track of all past revisions and the
changes that were made in each revision.  Each revision is named by a
@dfn{revision ID}, whose format depends on the version control system;
in the simplest case, it is just an integer.
222 223

  To go beyond these basic concepts, you will need to understand three
224 225 226 227
aspects in which version control systems differ.  As explained in the
next three sections, they can be lock-based or merge-based; file-based
or changeset-based; and centralized or decentralized.  VC handles all
these modes of operation, but it cannot hide the differences.
228

229 230 231
@node VCS Merging
@subsubsection Merge-based vs lock-based Version Control

232 233 234 235
  A version control system typically has some mechanism to coordinate
between users who want to change the same file.  There are two ways to
do this: merging and locking.

236
@cindex merging-based version
237 238 239 240
  In a version control system that uses merging, each user may modify
a work file at any time.  The system lets you @dfn{merge} your work
file, which may contain changes that have not been committed, with the
latest changes that others have committed.
241

242
@cindex locking-based version
243 244 245 246 247 248
  Older version control systems use a @dfn{locking} scheme instead.
Here, work files are normally read-only.  To edit a file, you ask the
version control system to make it writable for you by @dfn{locking}
it; only one user can lock a given file at any given time.  This
procedure is analogous to, but different from, the locking that Emacs
uses to detect simultaneous editing of ordinary files
249
(@pxref{Interlocking}).  When you commit your changes, that unlocks
250 251 252 253 254 255 256
the file, and the work file becomes read-only again.  Other users may
then lock the file to make their own changes.

  Both locking and merging systems can have problems when multiple
users try to modify the same file at the same time.  Locking systems
have @dfn{lock conflicts}; a user may try to check a file out and be
unable to because it is locked.  In merging systems, @dfn{merge
257 258
conflicts} happen when you commit a change to a file that conflicts
with a change committed by someone else after your checkout.  Both
259
kinds of conflict have to be resolved by human judgment and
260 261 262
communication.  Experience has shown that merging is superior to
locking, both in convenience to developers and in minimizing the
number and severity of conflicts that actually occur.
263 264 265 266

  SCCS always uses locking.  RCS is lock-based by default but can be
told to operate in a merging style.  CVS and Subversion are
merge-based by default but can be told to operate in a locking mode.
267
Decentralized version control systems, such as GNU Arch, Git, and
268
Mercurial, are exclusively merging-based.
269

270
  VC mode supports both locking and merging version control.  The
271 272 273 274 275 276 277
terms ``commit'' and ``update'' are used in newer version control
systems; older lock-based systems use the terms ``check in'' and
``check out''.  VC hides the differences between them as much as
possible.

@node VCS Changesets
@subsubsection Changeset-based vs File-based Version Control
278

279
@cindex file-based version control
280 281
  On SCCS, RCS, CVS, and other early version control systems, version
control operations are @dfn{file-based}: each file has its own comment
282 283
and revision history separate from that of all other files.  Newer
systems, beginning with Subversion, are @dfn{changeset-based}: a
284
commit may include changes to several files, and the entire set of
285 286
changes is handled as a unit.  Any comment associated with the change
does not belong to a single file, but to the changeset itself.
287

288
@cindex changeset-based version control
289 290 291
  Changeset-based version control is more flexible and powerful than
file-based version control; usually, when a change to multiple files
has to be reversed, it's good to be able to easily identify and remove
292
all of it.
293

294 295 296 297 298
@node VCS Repositories
@subsubsection Decentralized vs Centralized Repositories

@cindex centralized version control
@cindex decentralized version control
299
@cindex distributed version control
300 301 302
  Early version control systems were designed around a
@dfn{centralized} model in which each project has only one repository
used by all developers.  SCCS, RCS, CVS, and Subversion share this
303 304
kind of model.  One of its drawbacks is that the repository is a choke
point for reliability and efficiency.
305

306 307 308 309 310 311 312
  GNU Arch pioneered the concept of @dfn{distributed} or
@dfn{decentralized} version control, later implemented in Git,
Mercurial, and Bazaar.  A project may have several different
repositories, and these systems support a sort of super-merge between
repositories that tries to reconcile their change histories.  In
effect, there is one repository for each developer, and repository
merges take the place of commit operations.
313

314 315 316
  VC helps you manage the traffic between your personal workfiles and
a repository.  Whether the repository is a single master, or one of a
network of peer repositories, is not something VC has to care about.
317 318 319 320 321 322 323 324 325

@node Types of Log File
@subsubsection Types of Log File
@cindex types of log file
@cindex log File, types of
@cindex version control log

  Projects that use a version control system can have two types of log
for changes.  One is the log maintained by the version control system:
326 327 328
each time you commit a change, you fill out a @dfn{log entry} for the
change (@pxref{Log Buffer}).  This is called the @dfn{version control
log}.
329 330 331 332 333 334

  The other kind of log is the file @file{ChangeLog} (@pxref{Change
Log}).  It provides a chronological record of all changes to a large
portion of a program---typically one directory and its subdirectories.
A small program would use one @file{ChangeLog} file; a large program
may have a @file{ChangeLog} file in each major directory.
335 336 337 338 339 340 341 342
@xref{Change Log}.  Programmers have used change logs since long
before version control systems.

  Changeset-based version systems typically maintain a changeset-based
modification log for the entire system, which makes change log files
somewhat redundant.  One advantage that they retain is that it is
sometimes useful to be able to view the transaction history of a
single directory separately from those of other directories.
343 344 345 346 347 348 349 350 351

  A project maintained with version control can use just the version
control log, or it can use both kinds of logs.  It can handle some
files one way and some files the other way.  Each project has its
policy, which you should follow.

  When the policy is to use both, you typically want to write an entry
for each change just once, then put it into both logs.  You can write
the entry in @file{ChangeLog}, then copy it to the log buffer with
352 353 354
@kbd{C-c C-a} when committing the change (@pxref{Log Buffer}).  Or you
can write the entry in the log buffer while committing the change, and
later use the @kbd{C-x v a} command to copy it to @file{ChangeLog}
355 356 357 358 359 360 361 362 363
@iftex
(@pxref{Change Logs and VC,,,emacs-xtra, Specialized Emacs Features}).
@end iftex
@ifnottex
(@pxref{Change Logs and VC}).
@end ifnottex

@node VC Mode Line
@subsection Version Control and the Mode Line
364
@cindex VC mode line indicator
365 366

  When you visit a file that is under version control, Emacs indicates
367 368
this on the mode line.  For example, @samp{Bzr-1223} says that Bazaar
is used for that file, and the current revision ID is 1223.
369

370
@cindex version control status
371
  The character between the back-end name and the revision ID
372 373 374 375 376 377 378 379
indicates the @dfn{version control status} of the work file.  In a
merge-based version control system, a @samp{-} character indicates
that the work file is unmodified, and @samp{:} indicates that it has
been modified.  @samp{!} indicates that the file contains conflicts as
result of a recent merge operation (@pxref{Merging}), or that the file
was removed from the version control.  Finally, @samp{?}  means that
the file is under version control, but is missing from the working
tree.
380 381 382

  In a lock-based system, @samp{-} indicates an unlocked file, and
@samp{:} a locked file; if the file is locked by another user (for
383
instance, @samp{jim}), that is displayed as @samp{RCS:jim:1.3}.
384
@samp{@@} means that the file was locally added, but not yet committed
385
to the master repository.
386 387 388 389

  On a graphical display, you can move the mouse over this mode line
indicator to pop up a ``tool-tip'', which displays a more verbose
description of the version control status.  Pressing @kbd{Mouse-1}
390 391
over the indicator pops up a menu of VC commands, identical to
@samp{Tools / Version Control} on the menu bar.
392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407

@vindex auto-revert-check-vc-info
  When Auto Revert mode (@pxref{Reverting}) reverts a buffer that is
under version control, it updates the version control information in
the mode line.  However, Auto Revert mode may not properly update this
information if the version control status changes without changes to
the work file, from outside the current Emacs session.  If you set
@code{auto-revert-check-vc-info} to @code{t}, Auto Revert mode updates
the version control status information every
@code{auto-revert-interval} seconds, even if the work file itself is
unchanged.  The resulting CPU usage depends on the version control
system, but is usually not excessive.

@node Basic VC Editing
@subsection Basic Editing under Version Control

408
@cindex filesets, VC
409
@cindex VC filesets
410
   Most VC commands operate on @dfn{VC filesets}.  A VC fileset is a
411 412 413 414
collection of one or more files that a VC operation acts on.  When you
type VC commands in a buffer visiting a version-controlled file, the
VC fileset is simply that one file.  When you type them in a VC
Directory buffer, and some files in it are marked, the VC fileset
415 416
consists of the marked files (@pxref{VC Directory Mode}).

417 418 419 420 421 422 423
  On modern changeset-based version control systems (@pxref{VCS
Changesets}), VC commands handle multi-file VC filesets as a group.
For example, committing a multi-file VC fileset generates a single
revision, containing the changes to all those files.  On older
file-based version control systems like CVS, each file in a multi-file
VC fileset is handled individually; for example, a commit generates
one revision for each changed file.
424 425 426

@table @kbd
@itemx C-x v v
427 428
Perform the next appropriate version control operation on the current
VC fileset.
429 430 431 432
@end table

@findex vc-next-action
@kindex C-x v v
433
  The principal VC command is a multi-purpose command, @kbd{C-x v v}
434 435 436 437 438 439 440 441 442 443 444
(@code{vc-next-action}), which performs the ``most appropriate''
action on the current VC fileset: either registering it with a version
control system, or committing it, or unlocking it, or merging changes
into it.  The precise actions are described in detail in the following
subsections.  You can use @kbd{C-x v v} either in a file-visiting
buffer or in a VC Directory buffer.

  Note that VC filesets are distinct from the ``named filesets'' used
for viewing and visiting files in functional groups
(@pxref{Filesets}).  Unlike named filesets, VC filesets are not named
and don't persist across sessions.
445 446 447 448 449 450 451 452 453 454

@menu
* VC With A Merging VCS::  Without locking: default mode for CVS.
* VC With A Locking VCS::  RCS in its default mode, SCCS, and optionally CVS.
* Advanced C-x v v::       Advanced features available with a prefix argument.
@end menu

@node VC With A Merging VCS
@subsubsection Basic Version Control with Merging

455 456
  On a merging-based version control system (i.e.@: most modern ones;
@pxref{VCS Merging}), @kbd{C-x v v} does the following:
457 458 459

@itemize @bullet
@item
460
If there is more than one file in the VC fileset and the files have
461 462 463
inconsistent version control statuses, signal an error.  (Note,
however, that a fileset is allowed to include both ``newly-added''
files and ``modified'' files; @pxref{Registering}.)
464 465

@item
466 467 468 469 470
If none of the files in the VC fileset are registered with a version
control system, register the VC fileset, i.e.@: place it under version
control.  @xref{Registering}.  If Emacs cannot find a system to
register under, it prompts for a repository type, creates a new
repository, and registers the VC fileset with it.
471 472

@item
473
If every work file in the VC fileset is unchanged, do nothing.
474 475

@item
476
If every work file in the VC fileset has been modified, commit the
477 478
changes.  To do this, Emacs pops up a @samp{*vc-log*} buffer; type the
desired log entry for the new revision, followed by @kbd{C-c C-c} to
479
commit.  @xref{Log Buffer}.
480 481 482

If committing to a shared repository, the commit may fail if the
repository that has been changed since your last update.  In that
483 484 485 486 487
case, you must perform an update before trying again.  On a
decentralized version control system, use @kbd{C-x v +} (@pxref{VC
Pull}) or @kbd{C-x v m} (@pxref{Merging}).  On a centralized version
control system, type @kbd{C-x v v} again to merge in the repository
changes.
488 489

@item
490 491 492
Finally, if you are using a centralized version control system, check
if each work file in the VC fileset is up-to-date.  If any file has
been changed in the repository, offer to update it.
493 494 495
@end itemize

  These rules also apply when you use RCS in its ``non-locking'' mode,
496
except that changes are not automatically merged from the repository.
497 498
Nothing informs you if another user has committed changes in the same
file since you began editing it; when you commit your revision, his
499 500
changes are removed (however, they remain in the repository and are
thus not irrevocably lost).  Therefore, you must verify that the
501
current revision is unchanged before committing your changes.  In
502 503 504
addition, locking is possible with RCS even in this mode: @kbd{C-x v
v} with an unmodified file locks the file, just as it does with RCS in
its normal locking mode (@pxref{VC With A Locking VCS}).
505 506 507 508

@node VC With A Locking VCS
@subsubsection Basic Version Control with Locking

509 510
  On a locking-based version control system (such as SCCS, and RCS in
its default mode), @kbd{C-x v v} does the following:
511

512
@itemize @bullet
513
@item
514
If there is more than one file in the VC fileset and the files have
515
inconsistent version control statuses, signal an error.
516 517 518

@item
If each file in the VC fileset is not registered with a version
519 520 521 522
control system, register the VC fileset.  @xref{Registering}.  If
Emacs cannot find a system to register under, it prompts for a
repository type, creates a new repository, and registers the VC
fileset with it.
523 524

@item
Paul Eggert's avatar
Paul Eggert committed
525
If each file is registered and unlocked, lock it and make it writable,
526
so that you can begin to edit it.
527 528

@item
529 530 531 532
If each file is locked by you and contains changes, commit the
changes.  To do this, Emacs pops up a @samp{*vc-log*} buffer; type the
desired log entry for the new revision, followed by @kbd{C-c C-c} to
commit (@pxref{Log Buffer}).
533 534

@item
535 536
If each file is locked by you, but you have not changed it, release
the lock and make the file read-only again.
537 538

@item
539 540 541 542
If each file is locked by another user, ask whether you want to
``steal the lock''.  If you say yes, the file becomes locked by you,
and a warning message is sent to the user who had formerly locked the
file.
543 544 545
@end itemize

  These rules also apply when you use CVS in locking mode, except
546
that CVS does not support stealing locks.
547 548 549 550

@node Advanced C-x v v
@subsubsection Advanced Control in @kbd{C-x v v}

551
@cindex revision ID in version control
552 553 554 555 556 557 558
  When you give a prefix argument to @code{vc-next-action} (@kbd{C-u
C-x v v}), it still performs the next logical version control
operation, but accepts additional arguments to specify precisely how
to do the operation.

@itemize @bullet
@item
559 560 561 562
@cindex specific version control system
You can specify the name of a version control system.  This is useful
if the fileset can be managed by more than one version control system,
and Emacs fails to detect the correct one.
563 564

@item
565
Otherwise, if using CVS or RCS, you can specify a revision ID.
566

567 568 569
If the fileset is modified (or locked), this makes Emacs commit with
that revision ID.  You can create a new branch by supplying an
appropriate revision ID (@pxref{Branches}).
570

571 572 573 574 575 576 577 578 579
If the fileset is unmodified (and unlocked), this checks the specified
revision into the working tree.  You can also specify a revision on
another branch by giving its revision or branch ID (@pxref{Switching
Branches}).  An empty argument (i.e.@: @kbd{C-u C-x v v @key{RET}})
checks out the latest (``head'') revision on the current branch.

This signals an error on a decentralized version control system.
Those systems do not let you specify your own revision IDs, nor do
they use the concept of ``checking out'' individual files.
580 581 582
@end itemize

@node Log Buffer
583 584
@subsection Features of the Log Entry Buffer

585 586 587 588
@cindex C-c C-c @r{(Log Edit mode)}
@findex log-edit-done
  When you tell VC to commit a change, it pops up a buffer named
@samp{*vc-log*}.  In this buffer, you should write a @dfn{log entry}
589
describing the changes you have made (@pxref{Why Version Control?}).
590 591
After you are done, type @kbd{C-c C-c} (@code{log-edit-done}) to exit
the buffer and commit the change, together with your log entry.
592

593 594 595 596 597 598 599 600
@cindex Log Edit mode
@cindex mode, Log Edit
@vindex vc-log-mode-hook
  The major mode for the @samp{*vc-log*} buffer is Log Edit mode, a
variant of Text mode (@pxref{Text Mode}).  On entering Log Edit mode,
Emacs runs the hooks @code{text-mode-hook} and @code{vc-log-mode-hook}
(@pxref{Hooks}).

601 602 603 604 605 606 607
  In the @samp{*vc-log*} buffer, you can write one or more @dfn{header
lines}, specifying additional information to be supplied to the
version control system.  Each header line must occupy a single line at
the top of the buffer; the first line that is not a header line is
treated as the start of the log entry.  For example, the following
header line states that the present change was not written by you, but
by another developer:
608

609 610 611
@smallexample
Author: J. R. Hacker <jrh@@example.com>
@end smallexample
612

613 614 615 616 617
@noindent
Apart from the @samp{Author} header, Emacs recognizes the headers
@samp{Date} (a manually-specified commit time) and @samp{Fixes} (a
reference to a bug fixed by the change).  Not all version control
systems recognize all headers: Bazaar recognizes all three headers,
618
while Git, Mercurial, and Monotone recognize only @samp{Author} and
619 620
@samp{Date}.  If you specify a header for a system that does not
support it, the header is treated as part of the log entry.
621

622
@kindex C-c C-f @r{(Log Edit mode)}
623
@findex log-edit-show-files
624
@kindex C-c C-d @r{(Log Edit mode)}
625
@findex log-edit-show-diff
626 627 628 629 630 631 632
  While in the @samp{*vc-log*} buffer, the ``current VC fileset'' is
considered to be the fileset that will be committed if you type
@w{@kbd{C-c C-c}}.  To view a list of the files in the VC fileset,
type @w{@kbd{C-c C-f}} (@code{log-edit-show-files}).  To view a diff
of changes between the VC fileset and the version from which you
started editing (@pxref{Old Revisions}), type @kbd{C-c C-d}
(@code{log-edit-show-diff}).
633

634 635
@kindex C-c C-a @r{(Log Edit mode)}
@findex log-edit-insert-changelog
636 637
  If the VC fileset includes one or more @file{ChangeLog} files
(@pxref{Change Log}), type @kbd{C-c C-a}
638
(@code{log-edit-insert-changelog}) to pull the relevant entries into
639
the @samp{*vc-log*} buffer.  If the topmost item in each
640
@file{ChangeLog} was made under your user name on the current date,
641 642
this command searches that item for entries matching the file(s) to be
committed, and inserts them.
643
@ifnottex
644 645 646
If you are using CVS or RCS, see @ref{Change Logs and VC}, for the
opposite way of working---generating ChangeLog entries from the Log
Edit buffer.
647 648
@end ifnottex

649
  To abort a commit, just @strong{don't} type @kbd{C-c C-c} in that
650
buffer.  You can switch buffers and do other editing.  As long as you
651 652 653 654 655 656 657 658
don't try to make another commit, the entry you were editing remains
in the @samp{*vc-log*} buffer, and you can go back to that buffer at
any time to complete the commit.

@kindex M-n @r{(Log Edit mode)}
@kindex M-p @r{(Log Edit mode)}
@kindex M-s @r{(Log Edit mode)}
@kindex M-r @r{(Log Edit mode)}
659
  You can also browse the history of previous log entries to duplicate
660 661 662 663 664
a commit comment.  This can be useful when you want to make several
commits with similar comments.  The commands @kbd{M-n}, @kbd{M-p},
@kbd{M-s} and @kbd{M-r} for doing this work just like the minibuffer
history commands (@pxref{Minibuffer History}), except that they are
used outside the minibuffer.
665

666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705
@node Registering
@subsection Registering a File for Version Control

@table @kbd
@item C-x v i
Register the visited file for version control.
@end table

@kindex C-x v i
@findex vc-register
  The command @kbd{C-x v i} (@code{vc-register}) @dfn{registers} each
file in the current VC fileset, placing it under version control.
This is essentially equivalent to the action of @kbd{C-x v v} on an
unregistered VC fileset (@pxref{Basic VC Editing}), except that if the
VC fileset is already registered, @kbd{C-x v i} signals an error
whereas @kbd{C-x v v} performs some other action.

  To register a file, Emacs must choose a version control system.  For
a multi-file VC fileset, the VC Directory buffer specifies the system
to use (@pxref{VC Directory Mode}).  For a single-file VC fileset, if
the file's directory already contains files registered in a version
control system, or if the directory is part of a directory tree
controlled by a version control system, Emacs chooses that system.  In
the event that more than one version control system is applicable,
Emacs uses the one that appears first in the variable
@iftex
@code{vc-handled-backends}.
@end iftex
@ifnottex
@code{vc-handled-backends} (@pxref{Customizing VC}).
@end ifnottex
If Emacs cannot find a version control system to register the file
under, it prompts for a repository type, creates a new repository, and
registers the file into that repository.

  On most version control systems, registering a file with @kbd{C-x v
i} or @kbd{C-x v v} adds it to the ``working tree'' but not to the
repository.  Such files are labeled as @samp{added} in the VC
Directory buffer, and show a revision ID of @samp{@@@@} in the mode
line.  To make the registration take effect in the repository, you
706 707
must perform a commit (@pxref{Basic VC Editing}).  Note that a single
commit can include both file additions and edits to existing files.
708 709 710 711

  On a locking-based version control system (@pxref{VCS Merging}),
registering a file leaves it unlocked and read-only.  Type @kbd{C-x v
v} if you wish to start editing it.
712 713 714 715 716 717

@node Old Revisions
@subsection Examining And Comparing Old Revisions

@table @kbd
@item C-x v =
718 719 720 721 722 723 724
Compare the work files in the current VC fileset with the versions you
started from (@code{vc-diff}).  With a prefix argument, prompt for two
revisions of the current VC fileset and compare them.  You can also
call this command from a Dired buffer (@pxref{Dired}).

@ifnottex
@item M-x vc-ediff
725 726
Like @kbd{C-x v =}, but using Ediff.  @xref{Top, Ediff, ediff, The
Ediff Manual}.
727
@end ifnottex
728 729

@item C-x v D
730 731 732
Compare the entire working tree to the revision you started from
(@code{vc-root-diff}).  With a prefix argument, prompt for two
revisions and compare their trees.
733 734 735 736

@item C-x v ~
Prompt for a revision of the current file, and visit it in a separate
buffer (@code{vc-revision-other-window}).
737 738

@item C-x v g
739 740
Display an annotated version of the current file: for each line, show
the latest revision in which it was modified (@code{vc-annotate}).
741 742 743 744
@end table

@findex vc-diff
@kindex C-x v =
745 746 747 748 749 750 751
  @kbd{C-x v =} (@code{vc-diff}) displays a @dfn{diff} which compares
each work file in the current VC fileset to the version(s) from which
you started editing.  The diff is displayed in another window, in a
Diff mode buffer (@pxref{Diff Mode}) named @file{*vc-diff*}.  The
usual Diff mode commands are available in this buffer.  In particular,
the @kbd{g} (@code{revert-buffer}) command performs the file
comparison again, generating a new diff.
752

753 754 755
@kindex C-u C-x v =
  To compare two arbitrary revisions of the current VC fileset, call
@code{vc-diff} with a prefix argument: @kbd{C-u C-x v =}.  This
756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773
prompts for two revision IDs (@pxref{VCS Concepts}), and displays a
diff between those versions of the fileset.  This will not work
reliably for multi-file VC filesets, if the version control system is
file-based rather than changeset-based (e.g.@: CVS), since then
revision IDs for different files would not be related in any
meaningful way.

  Instead of the revision ID, some version control systems let you
specify revisions in other formats.  For instance, under Bazaar you
can enter @samp{date:yesterday} for the argument to @kbd{C-u C-x v =}
(and related commands) to specify the first revision committed after
yesterday.  See the documentation of the version control system for
details.

  If you invoke @kbd{C-x v =} or @kbd{C-u C-x v =} from a Dired buffer
(@pxref{Dired}), the file listed on the current line is treated as the
current VC fileset.

774
@ifnottex
775 776 777
@findex vc-ediff
  @kbd{M-x vc-ediff} works like @kbd{C-x v =}, except that it uses an
Ediff session.  @xref{Top, Ediff, ediff, The Ediff Manual}.
778 779
@end ifnottex

780 781 782
@findex vc-root-diff
@kindex C-x v D
  @kbd{C-x v D} (@code{vc-root-diff}) is similar to @kbd{C-x v =}, but
783 784 785 786
it displays the changes in the entire current working tree (i.e.@: the
working tree containing the current VC fileset).  If you invoke this
command from a Dired buffer, it applies to the working tree containing
the directory.
787

788
@vindex vc-diff-switches
789 790 791 792 793
  You can customize the @command{diff} options that @kbd{C-x v =} and
@kbd{C-x v D} use for generating diffs.  The options used are taken
from the first non-@code{nil} value amongst the variables
@code{vc-@var{backend}-diff-switches}, @code{vc-diff-switches}, and
@code{diff-switches} (@pxref{Comparing Files}), in that order.  Here,
794
@var{backend} stands for the relevant version control system,
795 796 797 798
e.g.@: @code{bzr} for Bazaar.  Since @code{nil} means to check the
next variable in the sequence, either of the first two may use the
value @code{t} to mean no switches at all.  Most of the
@code{vc-@var{backend}-diff-switches} variables default to @code{nil},
799 800 801
but some default to @code{t}; these are for version control systems
whose @code{diff} implementations do not accept common diff options,
such as Subversion.
802 803 804 805 806 807 808 809 810

@findex vc-revision-other-window
@kindex C-x v ~
  To directly examine an older version of a file, visit the work file
and type @kbd{C-x v ~ @var{revision} @key{RET}}
(@code{vc-revision-other-window}).  This retrieves the file version
corresponding to @var{revision}, saves it to
@file{@var{filename}.~@var{revision}~}, and visits it in a separate
window.
811 812 813

@findex vc-annotate
@kindex C-x v g
814 815
  Many version control systems allow you to view files @dfn{annotated}
with per-line revision information, by typing @kbd{C-x v g}
816
(@code{vc-annotate}).  This creates a new buffer (the ``annotate
817 818 819 820 821
buffer'') displaying the file's text, with each line colored to show
how old it is.  Red text is new, blue is old, and intermediate colors
indicate intermediate ages.  By default, the color is scaled over the
full range of ages, such that the oldest changes are blue, and the
newest changes are red.
822 823

  When you give a prefix argument to this command, Emacs reads two
824 825 826
arguments using the minibuffer: the revision to display and annotate
(instead of the current file contents), and the time span in days the
color range should cover.
827 828 829 830 831 832 833 834

  From the annotate buffer, these and other color scaling options are
available from the @samp{VC-Annotate} menu.  In this buffer, you can
also use the following keys to browse the annotations of past revisions,
view diffs, or view log entries:

@table @kbd
@item p
835 836 837
Annotate the previous revision, i.e.@: the revision before the one
currently annotated.  A numeric prefix argument is a repeat count, so
@kbd{C-u 10 p} would take you back 10 revisions.
838 839

@item n
840 841
Annotate the next revision, i.e.@: the revision after the one
currently annotated.  A numeric prefix argument is a repeat count.
842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879

@item j
Annotate the revision indicated by the current line.

@item a
Annotate the revision before the one indicated by the current line.
This is useful to see the state the file was in before the change on
the current line was made.

@item f
Show in a buffer the file revision indicated by the current line.

@item d
Display the diff between the current line's revision and the previous
revision.  This is useful to see what the current line's revision
actually changed in the file.

@item D
Display the diff between the current line's revision and the previous
revision for all files in the changeset (for VC systems that support
changesets).  This is useful to see what the current line's revision
actually changed in the tree.

@item l
Show the log of the current line's revision.  This is useful to see
the author's description of the changes in the revision on the current
line.

@item w
Annotate the working revision--the one you are editing.  If you used
@kbd{p} and @kbd{n} to browse to other revisions, use this key to
return to your working revision.

@item v
Toggle the annotation visibility.  This is useful for looking just at
the file contents without distraction from the annotations.
@end table

880
@node VC Change Log
881
@subsection VC Change Log
882 883 884

@table @kbd
@item C-x v l
885
Display the change history for the current fileset
886 887 888 889 890
(@code{vc-print-log}).

@item C-x v L
Display the change history for the current repository
(@code{vc-print-root-log}).
891 892 893 894 895 896 897 898

@item C-x v I
Display the changes that will be received with a pull operation
(@code{vc-log-incoming}).

@item C-x v O
Display the changes that will be sent by the next push operation
(@code{vc-log-outgoing}).
899 900 901 902
@end table

@kindex C-x v l
@findex vc-print-log
903
  The command @kbd{C-x v l} (@code{vc-print-log}) displays a buffer
904 905 906 907 908 909 910 911 912 913 914
named @samp{*vc-change-log*}, showing the history of changes made to
the current file, including who made the changes, the dates, and the
log entry for each change (these are the same log entries you would
enter via the @samp{*vc-log*} buffer; @pxref{Log Buffer}).  Point is
centered at the revision of the file currently being visited.  With a
prefix argument, the command prompts for the revision to center on,
and the maximum number of revisions to display.

  If you call @kbd{C-x v l} from a VC Directory buffer (@pxref{VC
Directory Mode}) or a Dired buffer (@pxref{Dired}), it applies to the
file listed on the current line.
915 916

@findex vc-print-root-log
917 918 919 920 921 922 923 924
@findex log-view-toggle-entry-display
  @kbd{C-x v L} (@code{vc-print-root-log}) displays a
@samp{*vc-change-log*} buffer showing the history of the entire
version-controlled directory tree (RCS, SCCS, and CVS do not support
this feature).  With a prefix argument, the command prompts for the
maximum number of revisions to display.

  The @kbd{C-x v L} history is shown in a compact form, usually
925 926
showing only the first line of each log entry.  However, you can type
@key{RET} (@code{log-view-toggle-entry-display}) in the
927 928
@samp{*vc-change-log*} buffer to reveal the entire log entry for the
revision at point.  A second @key{RET} hides it again.
929

930
  On a decentralized version control system, the @kbd{C-x v I}
931 932 933
(@code{vc-log-incoming}) command displays a log buffer showing the
changes that will be applied, the next time you run the version
control system's ``pull'' command to get new revisions from another
934 935 936 937 938 939 940
repository (@pxref{VC Pull}).  This other repository is the default
one from which changes are pulled, as defined by the version control
system; with a prefix argument, @code{vc-log-incoming} prompts for a
specific repository.  Similarly, @kbd{C-x v O}
(@code{vc-log-outgoing}) shows the changes that will be sent to
another repository, the next time you run the ``push'' command; with a
prefix argument, it prompts for a specific destination repository.
941

942
  In the @samp{*vc-change-log*} buffer, you can use the following keys
943 944
to move between the logs of revisions and of files, and to examine and
compare past revisions (@pxref{Old Revisions}):
945 946 947

@table @kbd
@item p
948
Move to the previous revision entry.  (Revision entries in the log
949 950 951 952 953
buffer are usually in reverse-chronological order, so the previous
revision-item usually corresponds to a newer revision.)  A numeric
prefix argument is a repeat count.

@item n
954 955
Move to the next revision entry.  A numeric prefix argument is a
repeat count.
956 957

@item P
958 959 960
Move to the log of the previous file, if showing logs for a multi-file
VC fileset.  Otherwise, just move to the beginning of the log.  A
numeric prefix argument is a repeat count.
961 962

@item N
963 964
Move to the log of the next file, if showing logs for a multi-file VC
fileset.  A numeric prefix argument is a repeat count.
965 966

@item a
967
Annotate the revision on the current line (@pxref{Old Revisions}).
968 969 970 971 972 973

@item e
Modify the change comment displayed at point.  Note that not all VC
systems support modifying change comments.

@item f
974
Visit the revision indicated at the current line.
975 976

@item d
977 978
Display a diff between the revision at point and the next earlier
revision, for the specific file.
979 980

@item D
981 982 983 984 985 986 987 988
Display the changeset diff between the revision at point and the next
earlier revision.  This shows the changes to all files made in that
revision.

@item @key{RET}
In a compact-style log buffer (e.g.@: the one created by @kbd{C-x v
L}), toggle between showing and hiding the full log entry for the
revision at point.
989 990
@end table

991 992 993 994 995 996 997 998 999 1000
@vindex vc-log-show-limit
Because fetching many log entries can be slow, the
@samp{*vc-change-log*} buffer displays no more than 2000 revisions by
default.  The variable @code{vc-log-show-limit} specifies this limit;
if you set the value to zero, that removes the limit.  You can also
increase the number of revisions shown in an existing
@samp{*vc-change-log*} buffer by clicking on the @samp{Show 2X
entries} or @samp{Show unlimited entries} buttons at the end of the
buffer.  However, RCS, SCCS, and CVS do not support this feature.

1001
@node VC Undo
1002
@subsection Undoing Version Control Actions
1003 1004 1005

@table @kbd
@item C-x v u
1006 1007
Revert the work file(s) in the current VC fileset to the last revision
(@code{vc-revert}).
1008 1009
@end table

1010 1011
@c `C-x v c' (vc-rollback) was removed, since it's RCS/SCCS specific.

1012
@kindex C-x v u
1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028
@findex vc-revert
@vindex vc-revert-show-diff
  If you want to discard all the changes you have made to the current
VC fileset, type @kbd{C-x v u} (@code{vc-revert-buffer}).  This shows
you a diff between the work file(s) and the revision from which you
started editing, and asks for confirmation for discarding the changes.
If you agree, the fileset is reverted.  If you don't want @kbd{C-x v
u} to show a diff, set the variable @code{vc-revert-show-diff} to
@code{nil} (you can still view the diff directly with @kbd{C-x v =};
@pxref{Old Revisions}).  Note that @kbd{C-x v u} cannot be reversed
with the usual undo commands (@pxref{Undo}), so use it with care.

  On locking-based version control systems, @kbd{C-x v u} leaves files
unlocked; you must lock again to resume editing.  You can also use
@kbd{C-x v u} to unlock a file if you lock it and then decide not to
change it.
1029 1030 1031 1032

@node VC Directory Mode
@subsection VC Directory Mode

1033 1034 1035 1036 1037 1038 1039
@cindex VC Directory buffer
  The @dfn{VC Directory buffer} is a specialized buffer for viewing
the version control statuses of the files in a directory tree, and
performing version control operations on those files.  In particular,
it is used to specify multi-file VC filesets for commands like
@w{@kbd{C-x v v}} to act on (@pxref{VC Directory Commands}).