let commands that show changesets use templates. mechanism is same as hgweb templates. old show_changeset code is still used for now if no template given, because it is faster than template code when verbose or debug. simple template can be given on command line using -t, --template. example: hg log -t '{author|person}\n' complex template can be put in template map file, given on command line using --map-file. we give two example map files: map-log.compact prints 3 lines of output for every change. map-log.verbose prints exact same output as default "hg log -v". map files are searched where user says, then in template path as backup. example: hg log --map-file map-log.compact defaults can be set in hgrc with ui.logtemplate and ui.logmap.

     1

pulling from ../B1

     2

searching for changes

     3

adding changesets

     4

adding manifests

     5

adding file changes

     6

added 1 changesets with 1 changes to 1 files (+1 heads)

     7

(run 'hg update' to get a working copy)

     8

bar should remain deleted.

     9

f9b0e817f6a48de3564c6b2957687c5e7297c5a0 644 foo

    10

pulling from ../A2

    11

searching for changes

    12

adding changesets

    13

adding manifests

    14

adding file changes

    15

added 1 changesets with 0 changes to 0 files (+1 heads)

    16

(run 'hg update' to get a working copy)

    17

bar should remain deleted.

    18

f9b0e817f6a48de3564c6b2957687c5e7297c5a0 644 foo