default ignores don't ignore '.swp'
Aaron Bentley
aaron.bentley at utoronto.ca
Mon Jan 9 19:15:37 GMT 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Arbash Meinel wrote:
> I'm a little against dumping all ignore patterns into
> .bzrignore, because there are quite a few, and it makes the file a
> little ugly.
We're already doing that, though.
> Also, a bzr upgrade can do something like make .DS_Store ignored
> everywhere, rather than having to manually do it in every project that
> now has a non-default ignore set.
Yes, there are other situations where it's handy to add new default
ignores, too. But if I have to chose between default-ignoring new types
and being able to override defaults, I'll take the latter. I'd be
happier if I didn't have to make that choice.
> If you know of any real-world projects that use .pyc files as source,
> then we certainly can consider removing them from the default ignore
> list. But for the same reason we default to ignoring *.o, (and possibly
> *.obj) is that the chance of them being source is very low.
I don't at the moment, but there are lots of cases in developing
proprietary software where all you have is a .a or .so. I assume it
will happen to Python software, sooner or later.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDwrZZ0F+nu1YWqI0RArWfAJ9aPVW6q0JfcDxw6K9Uyvc+9cirwwCeK/Jr
BmcY7qypJiUPTcJ7Ow86qKg=
=ukee
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list