.bzrignore -> .bzrmeta/ignore

[Gordon Tyler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gordon Tyler wrote:
> lp:~doxxx/bzr/bzrmeta-ignore
> 
> This is the first stage of my branch converting .bzrignore to
> .bzrmeta/ignore. It does not have any backwards-compatibility handling
> of .bzrignore which is the next stage I will be tackling. All tests pass
> and I've updated the docs except the non-English stuff.
> 
> If .bzrignore exists and 'bzr ignore blah' is used to add an ignore
> pattern, should it add it to the existing .bzrignore or should it
> convert the .bzrignore to .bzrmeta/ignore and add the new pattern to that?

I've just updated this branch to add backwards compatibility support for
.bzrignore files. If a .bzrignore file exists, it will be read in
addition to the .bzrmeta/ignore file. Updates to the ignore patterns for
a tree will try to update .bzrignore first if it exists, otherwise
.bzrmeta/ignore will be created/updated.

Robert Collins mentioned on IRC that forwards compatibility is
problematic. For example, a branch is created using the current bzr with
a .bzrmeta/ignore file but then the branch is checked out by a user
using an older version of bzr. This user will not be able to make use of
the .bzrmeta/ignore file unless they copy or symlink it to .bzrignore.

Any comments?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLFvqaAAoJEIrPJfWinA2uRw0H/0G6NbNb5gdAmnuGUBzJbTXn
hyLBAJvpwoOQG5BvMVpk8yjF/neF8EwfHXrO03/GtN4OGBl/nTq8fNaoA9H8hVms
Sd7ebpAQMD9tXt6sceAJWl0XdZOZV3tjwy8ISPh4/4pkE1+2tfptNWzkuOaK9DA3
1IITzjyoj7j+mHHQcHAPU0pvzoooQwKd3vMDuvOrhQsDxwQFoiCjKWBiW16ZGVw5
0gwRPc2762TuZ6hftTT0EebsvUpXTx7i3GVRxwgJqnxZNvia/R3uIvU06HX5usPC
GY2pC8O++Ems7jBLLhG4XCULVYXVjgus1PXlYO7QNaZYF3FOBJOdsBBq4nG8Em8=
=l+tN
-----END PGP SIGNATURE-----