default ignores don't ignore '.swp'

Robert Collins robertc at
Mon Jan 9 22:14:07 GMT 2006

On Mon, 2006-01-09 at 14:09 -0800, Robey Pointer wrote:
> On 9 Jan 2006, at 13:24, Aaron Bentley wrote:
> > For me, it comes back to "the defaults should be *default*, not
> > *mandatory*".  But okay, let's not overreact.  We can pull
> > from the default ignores, since that's the immediate request.
> >
> > Does anyone else have ideas about how we should handle this?
> I agree with your statement above.  I want to be able to remove  
> elements from .bzrignore as well as add them.  Maybe I want to check  
> in .pyc files for some nefarious reason.  bzr shouldn't force this  
> kind of thing on people.

Right, my preference is what we did in tla - we write the ignores
default list to disk on tree initialisation and thereafter do nothing.

With format upgrades we can vary this: write new/remove deleted defaults
from the tree ignore list when upgrade is run.

I.e. when 'bzr upgrade' is run on our next upgrade, the current
mandatory defaults are written to disk, and the ignore logic for that
format tree only uses what the tree says.


GPG key available at: <>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : 

More information about the bazaar mailing list