[fixed] ignore problem

[Martin Pool]

On 9 April 2011 03:02, vila <v.ladeuil+lp at free.fr> wrote:
>>>>>> Steve Franks <bahamasfranks at gmail.com> writes:
>
>    >> 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.
>
>    > I came around to exactly that line of thinking after analyzing the
>    > problem for a few more minutes myself.  I had this occur once before,
>    > and I never figured out the problem was related to ignore until now -
>    > guess I should have added a few more -v 's the first time around...
>
> May be 'bzr add' should mention 'bzr ignored' when it is invoked without
> arguments and add *no* files.
>
> Would that have helped you ?

We've gone around things like that a few times before and I think
generally trying to guess at the user's problem in cases like that
doesn't work very well.

What might work well is:

 - have ``bzr add -vv`` show what's being ignored and why
 - have ``bzr help add`` point you to ``bzr ignored`` as a way to find
out why things are ignored