Status update & proposed direction for branch-specific rules

[Jelmer Vernooij]

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

Hi Ian,

Ian Clatworthy wrote:
> 3. Design and implement an out-of-tree-but-versioned solution for
> rules, ignores and anything else that needs it. This may take a
> long time to do, but then again it may not, depending on how it
> hangs together.
>
> I'm going to have a crack at #3 and if that doesn't fly, argue for
> #1. I've had some thoughts over the weekend that I've written those
>  up as a draft spec. See
> http://bazaar-vcs.org/DraftSpecs/MetafileManagement.
>
> Thoughts?
Where would these files be stored and referenced exactly inside of the
repository? Will they show up in the contents of RevisionTree, or will
the RevisionTree API rather have functions to check if e.g. a file is
ignored?

My main objection to the original .bzrrules implementation was the
fact that .bzrignore and .bzrrules appear in the user tree that ends
up being versioned, basically making it impossible to ever change
their format and making it very hard to do conversions  to and from
other systems.

I don't particularly mind .bzrignore or .bzrrules living in the root
of the working tree, other than that it makes it harder for "user"
files with those names to exist.

Cheers,

Jelmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iJwEAQECAAYFAkoIRicACgkQDLQl4QYPZuWxNQP6A1yX8TRoiCe2QwWFp9EIKPgF
LSqIAXgTI/MgUYjR8EHKbcna0R1C6qIphSQ8307GBFk5Ile+CcJqtzZpSavqIlrr
AJe7gesuKG/hIDgBkekRnokTxpelvOSsbzL+GwKw8y0quqfXtBAHhnbifVAC75z5
Yhfm2syYC6BmLabLXyg=
=Ebm/
-----END PGP SIGNATURE-----