[MERGE] do not export .bzrrules

[John Arbash Meinel]

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

Christophe TROESTLER wrote:
| On Tue, 29 Jul 2008 09:36:13 -0500, John Arbash Meinel wrote:
|> Ian Clatworthy wrote:
|> | Currently, the export command skips over .bzrignore. This
|> | simple patch extends that logic so that other "magic"
|> | files in the .bzr* namespace - like .bzrrules - are
|> | skipped over during export as well.
|>
|> The only problem I know is that there are plugins which create
|> ".bzr-FOO" directories. (...)
|
| I do not know which plugings do that but, if these directories are not
| supposed to be versioned, couldn't it be recommended that they create
| .bzr/plugins/FOO instead?
|
| My 0.02€,
| ChriS
|
|

They are meant to be versioned. As I understand it, the users wanted a
way of propagating defaults, etc for plugins out to their users. So they
create ".bzr-<plugin>/" directories and drop in settings for the plugin.
Then it gets versioned and propagated via push/pull/merge.

But they don't actually consider it part of their source tree, and so
they don't want it in their "bzr export".

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiQf1sACgkQJdeBCYSNAAO/nACgy6FqdC+PfD+Vl0YUkTql1AmH
bMEAoNOiqOWto/vq1fMGXD3Iij+8tO6W
=FCSR
-----END PGP SIGNATURE-----