ignore patterns

[John Arbash Meinel]

Adam Mercer wrote:
> On 26/03/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
> 
>> You may need a newer 'bzr' to support '**'. But the other question is,
>> why not ignore "*.lo" everywhere with just a simple:
>>
>> *.lo
>>
>> Do you want to version them somewhere else?
> 
> Thats what I've done now, I initially wanted to be more specfic in
> case I needed to version any *.lo files at a later date. But with that
> being unlikely I've just ignored all *.lo files as you and Martin have
> suggested.
> 
> Cheers
> 
> Adam
> 

By the way, bzr ignore patterns are just advisory. So if you ignore
'*.lo' you can always 'bzr add foo.lo'. Explicitly versioning a file
takes precedence to ignoring it.

Ignoring has the following effects (FAQ?)

1) 'bzr add' or 'bzr add dir' will not automatically add them when it is
recursing and adding any 'unknown' files. 'bzr add foo' will always add
'foo', though.

2) 'bzr status' shows unknown files, but not ignored files

3) 'bzr commit --strict' will abort if there are unknown files, but not
if there are ignored files

4) 'bzr ls --unknown' versus 'bzr ls --ignored'

5) (from bzrtools), 'bzr clean-tree' will delete unknown files, 'bzr
clean-tree --ignored' will delete unknowns and ignored files.

Is there any other effect from ignoring files?

John
=:->