[fixed] ignore problem

[Stephen J. Turnbull]

Andrew Bennetts writes:

 > I think the main reason we don't support a .bzrignore file per directory
 > is performance: having to search for many files is going to be much
 > slower than looking for exactly one.

That's true, but it doesn't seem to bother git.

OTOH, it's never bothered me that bzr doesn't support per directory
ignore files; if per-directory ignores are needed, the "path included"
syntax is sufficiently flexible.  I've also stopped using them in git,
because it's too easy for me to forget they're there unless I use them
a lot, which I don't, and git also supports paths in patterns.

The real problem here is the rules like "*back*".  In general I would
say it's a bad idea to have an ignore pattern that's not anchored at
at least one end, or by "delimiter" characters like period or hyphen.
Such rules will bite you occasionally, and then the hack you use to
workaround them will turn around and cause you to add files with names
like "Backup of some file hardly needing tracking in the first place".