comparison mercurial/commands.py @ 7307:56380212d630

help: commands supporting --git point to the gitdiffs topic (issue1352)

7306:8e46e59aaf4c

    to its parent.

    Without the -a option, diff will avoid generating diffs of files
    it detects as binary. With -a, diff will generate a diff anyway,
    probably with undesirable results.
    """
    node1, node2 = cmdutil.revpair(repo, opts.get('rev'))

    m = cmdutil.match(repo, pats, opts)
    patch.diff(repo, node1, node2, match=m, opts=patch.diffopts(ui, opts))

    %r   zero-padded changeset revision number

    Without the -a option, export will avoid generating diffs of files
    it detects as binary. With -a, export will generate a diff anyway,
    probably with undesirable results.

    With the --switch-parent option, the diff will be against the second
    parent. It can be useful to review a merge.
    """
    if not changesets:

7307:56380212d630

    to its parent.

    Without the -a option, diff will avoid generating diffs of files
    it detects as binary. With -a, diff will generate a diff anyway,
    probably with undesirable results.

    Use the --git option to generate diffs in the git extended diff
    format. Read the gitdiffs help topic for more information.
    """
    node1, node2 = cmdutil.revpair(repo, opts.get('rev'))

    m = cmdutil.match(repo, pats, opts)
    patch.diff(repo, node1, node2, match=m, opts=patch.diffopts(ui, opts))

    %r   zero-padded changeset revision number

    Without the -a option, export will avoid generating diffs of files
    it detects as binary. With -a, export will generate a diff anyway,
    probably with undesirable results.

    Use the --git option to generate diffs in the git extended diff
    format. Read the gitdiffs help topic for more information.

    With the --switch-parent option, the diff will be against the second
    parent. It can be useful to review a merge.
    """
    if not changesets: