.bzrrules in branch histories
Martin Pool
mbp at canonical.com
Mon Aug 11 02:23:33 BST 2008
On Fri, Aug 1, 2008 at 11:03 AM, Robert Collins
<robertc at robertcollins.net> wrote:
> So Ian is making great progress towards having a robust tree filtering
> facility which will allow keyword expansion, end-of-line translation and
> so on. The .bzrrules support is part of that by activating translation.
>
> I've expressed concerns in the past about having bzr metadata part of
> the versioned tree - .bzrignore is an example of this, and its somewhat
> problematic today.
>
> Currently .bzrrules will be happily versioned by bzr 1.6; I'd like to
> disable that - to have the rules support include .bzrrules in the list
> of control directory names (like .bzrshelf) so that it does not get
> versioned.
>
> This would do several things:
> - it would stop .bzrrules propogating
> - it would also prevent .bzrrules propogating into svn (see bug 145155)
> - prevent a bunch of small fallout like export having to change
>
> I think that this is fine: rules and tree filtering are a new feature;
> they are not baked yet, and I think its more important with a new
> feature to be conservative about the impact on the versioned-history
> than to roll out every aspect of it straight-up.
If this is not baked yet then I think it would be cleaner to remove
the feature of reading from this file, rather than specially blocking
it out from being committed. We could still perhaps allow a branch or
plugin for trying filters to turn it back on.
--
Martin <http://launchpad.net/~mbp/>
More information about the bazaar
mailing list