MANIFEST.in
author Matt Mackall <mpm@selenic.com>
Sat, 18 Jun 2011 16:52:51 -0500
branchstable
changeset 968 8d821e2fed38
parent 238 e4a389eca1b9
permissions -rw-r--r--
scmutil: switch match users to supplying contexts The most appropriate context is not always clearly defined. The obvious cases: For working directory commands, we use None For commands (eg annotate) with single revs, we use that revision The less obvious cases: For commands (eg status, diff) with a pair of revs, we use the second revision For commands that take a range (like log), we use None [ original upstream message ]

# $Id$

include tests/test-keyword tests/test-keyword.out

include MANIFEST.in