# HG changeset patch
# User Bryan O'Sullivan <bos@serpentine.com>
# Date 1176758545 25200
# Node ID d3dd1bedba3c587cbdeb18a2dc32d5fa870e86e6
# Parent  7f07aca44938d38b30ae8713946346123cdf97b6
Backed out changeset 7f07aca44938d38b30ae8713946346123cdf97b6
Bad behaviour has gone away.

diff -r 7f07aca44938 -r d3dd1bedba3c en/examples/filenames.glob.range.out
--- a/en/examples/filenames.glob.range.out	Mon Mar 26 21:58:24 2007 -0700
+++ b/en/examples/filenames.glob.range.out	Mon Apr 16 14:22:25 2007 -0700
@@ -1,7 +1,3 @@
 $ \textbf{hg status 'glob:**[nr-t]'}
-A examples/simple.py
 ? MANIFEST.in
-? examples/performant.py
-? src/watcher/_watcher.c
-? src/watcher/watcher.py
 ? src/xyzzy.txt
diff -r 7f07aca44938 -r d3dd1bedba3c en/filenames.tex
--- a/en/filenames.tex	Mon Mar 26 21:58:24 2007 -0700
+++ b/en/filenames.tex	Mon Apr 16 14:22:25 2007 -0700
@@ -152,15 +152,6 @@
 token.  This small example illustrates the difference between the two.
 \interaction{filenames.glob.star-starstar}
 
-When you're writing a glob pattern, bear in mind that Mercurial will
-treat a pattern that matches a directory name as ``match every file
-under that directory''.  For example, a glob pattern of
-``\texttt{**c}'' means \emph{both} ``match files ending in
-`\texttt{c}''' ``any file under all directories that end in
-`\texttt{c}'''.  I personally find this behaviour counterintuitive.
-If you need to write a pattern that means ``match \emph{only} files'',
-you'll need to express it as a regular expression instead; see below.
-
 \subsection{Regular expression matching with \texttt{re} patterns}
 
 Mercurial accepts the same regular expression syntax as the Python