[MERGE] no default ignores
Aaron Bentley
aaron.bentley at utoronto.ca
Mon Jun 12 15:18:48 BST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
> On Mon, 2006-06-12 at 09:41 -0400, Aaron Bentley wrote:
>>I will add that I never want to add .pyc files or vim editor backups, so
>>I would appreciate if init provided a minimal default .bzrignore.
>
>
> I spoke with Martin about this, and we agreed that providing no defaults
> made sense. The rationale is that no default we choose will be right for
> everyone, and its easy to customise and tweak, so its reasonable to go
> with no default.
I think this is overly boolean. No design choice we make will be right
for everyone, but still we work on bzr, in the hope that it will be
right for the vast majority of people.
You could argue that doing this would hurt performance, and I'd accept
that. But I think the number of people who want to version control .swp
files approaches zero, and asking them to remove '*.swp' from .bzrignore
or do 'bzr init --no-defaults' would not be unreasonable.
>>I think it might make sense to bump the format of the ignore file, so
>>that existing working trees would still use global ignores, but new and
>>upgraded working trees would not.
>
>
> This is a lot more involved that it sounds: at a minimum it involves a
> new repository format...
Why? It's just a file in the user's directory. Old bzrs won't
understand it, but new ones will. It seems like a better tradeoff than
having everyone's ignore lists break when they upgrade their bzr.
> Jan Hudec has done a lot of work on a clean way
> to transform .bzrignore into versioned data instead of being a versioned
> file, and I think we should continue with that with the intent to merge
> bits of it as they mature, or all of it eventually.
IIRC, you were the one who objected to any changes that might affect the
ignore list even slightly. It seems strange that you're now advocating
a change that will break everyone's ignore lists, without providing an
upgrade path.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEjXfI0F+nu1YWqI0RAg5XAKCCRImvCqeyAgg6F8ubEPfSGixdeACfefj1
XYc0Ag7xI7OSlFdu22mcams=
=btDh
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list