@@ -946,6 +946,7 @@ the file contents without distraction from the annotations.
946
946
947
947
@node VC Change Log
948
948
@subsection VC Change Log
949
+ @cindex VC change log
949
950
950
951
@table @kbd
951
952
@item C-x v l
@@ -993,15 +994,25 @@ version-controlled directory tree (RCS, SCCS, CVS, and SRC do not
993
994
support this feature). With a prefix argument, the command prompts
994
995
for the maximum number of revisions to display. A numeric prefix
995
996
argument specifies the maximum number of revisions without prompting.
996
- When the numeric prefix argument is @kbd {M-1 }, the command prompts
997
- for the revision ID, and displays its log entry with a diff of changes.
997
+ When the numeric prefix argument is 1, as in @w {@kbd {C-1 C-x v L }} or
998
+ @w {@kbd {C-u 1 C-x v L }}, the command prompts for the revision ID, and
999
+ displays the log entry of that revision together with the changes
1000
+ (diffs) it introduced. (Some less capable version control systems,
1001
+ such as RCS and CVS, don't have commands to show a revision log with
1002
+ its diffs; for them the command displays only the log entry, and you
1003
+ can request to show the diffs by typing @kbd {d } or @kbd {D }, see
1004
+ below.)
998
1005
999
1006
The @kbd {C-x v L } history is shown in a compact form, usually
1000
1007
showing only the first line of each log entry. However, you can type
1001
1008
@key {RET } (@code {log-view-toggle-entry-display }) in the
1002
1009
@file {*vc-change-log* } buffer to reveal the entire log entry for the
1003
1010
revision at point. A second @key {RET } hides it again.
1004
1011
1012
+ @kindex C-x v I
1013
+ @kindex C-x v O
1014
+ @findex vc-log-incoming
1015
+ @findex vc-log-outgoing
1005
1016
On a decentralized version control system, the @kbd {C-x v I }
1006
1017
(@code {vc-log-incoming }) command displays a log buffer showing the
1007
1018
changes that will be applied, the next time you run the version
@@ -1014,6 +1025,8 @@ specific repository. Similarly, @kbd{C-x v O}
1014
1025
another repository, the next time you run the push command; with a
1015
1026
prefix argument, it prompts for a specific destination repository.
1016
1027
1028
+ @cindex VC log buffer , commands in
1029
+ @cindex vc-log buffer
1017
1030
In the @file {*vc-change-log* } buffer, you can use the following keys
1018
1031
to move between the logs of revisions and of files, and to examine and
1019
1032
compare past revisions (@pxref {Old Revisions }):
@@ -1426,11 +1439,13 @@ Mercurial in its normal mode of operation, each branch has its own
1426
1439
working directory tree, so switching between branches just involves
1427
1440
switching directories. On Git, branches are normally @dfn {co-located }
1428
1441
in the same directory, and switching between branches is done using
1429
- the @command {git checkout } command, which changes the contents of the
1442
+ the @kbd {git checkout } command, which changes the contents of the
1430
1443
working tree to match the branch you switch to. Bazaar also supports
1431
- co-located branches, in which case the @command {bzr switch } command
1444
+ co-located branches, in which case the @kbd {bzr switch } command
1432
1445
will switch branches in the current directory. With Subversion, you
1433
- switch to another branch using the @command {svn switch } command.
1446
+ switch to another branch using the @kbd {svn switch } command. With
1447
+ Mercurial, command @kbd {hg update } is used to swith to another
1448
+ branch.
1434
1449
1435
1450
The VC command to switch to another branch in the current directory
1436
1451
is @kbd {C-x v r @var {branch-name } @key {RET }} (@code {vc-retrieve-tag }).
@@ -1477,8 +1492,8 @@ On a decentralized version control system, the command @kbd{C-x v P}
1477
1492
(@code {vc-push }) updates another location with changes from the
1478
1493
current branch. With a prefix argument, it prompts for the exact
1479
1494
version control command to run, which lets you specify where to push
1480
- changes; the default is @command {bzr push } with Bazaar, @command {git
1481
- push } with Git, and @command {hg push } with Mercurial. The default
1495
+ changes; the default is @kbd {bzr push } with Bazaar, @kbd {git
1496
+ push } with Git, and @kbd {hg push } with Mercurial. The default
1482
1497
commands always push to a default location determined by the version
1483
1498
control system from your branch configuration.
1484
1499
@@ -1507,11 +1522,11 @@ control system.
1507
1522
1508
1523
Amongst decentralized version control systems, @kbd {C-x v + } is
1509
1524
currently supported only by Bazaar, Git, and Mercurial. With Bazaar,
1510
- it calls @command {bzr pull } for ordinary branches (to pull from a
1511
- master branch into a mirroring branch), and @command {bzr update } for a
1525
+ it calls @kbd {bzr pull } for ordinary branches (to pull from a
1526
+ master branch into a mirroring branch), and @kbd {bzr update } for a
1512
1527
bound branch (to pull from a central repository). With Git, it calls
1513
- @command {git pull } to fetch changes from a remote repository and merge
1514
- it into the current branch. With Mercurial, it calls @command {hg pull
1528
+ @kbd {git pull } to fetch changes from a remote repository and merge
1529
+ it into the current branch. With Mercurial, it calls @kbd {hg pull
1515
1530
-u } to fetch changesets from the default remote repository and update
1516
1531
the working directory.
1517
1532
@@ -1542,11 +1557,12 @@ two branches.
1542
1557
1543
1558
On a decentralized version control system, merging is done with the
1544
1559
command @kbd {C-x v m } (@code {vc-merge }). On Bazaar, this prompts for
1545
- the exact arguments to pass to @command {bzr merge }, offering a
1560
+ the exact arguments to pass to @kbd {bzr merge }, offering a
1546
1561
sensible default if possible. On Git, this prompts for the name of a
1547
1562
branch to merge from, with completion (based on the branch names known
1548
- to the current repository). The output from running the merge command
1549
- is shown in a separate buffer.
1563
+ to the current repository). With Mercurial, this prompts for argument
1564
+ to pass to @kbd {hg merge }. The output from running the merge
1565
+ command is shown in a separate buffer.
1550
1566
1551
1567
On a centralized version control system like CVS, @kbd {C-x v m }
1552
1568
prompts for a branch ID, or a pair of revision IDs (@pxref {Switching
0 commit comments