.bzrignore -> .bzrmeta/ignore

[Ian Clatworthy]

Max Bowsher wrote:
> Ben Finney wrote:
>> Robert Collins writes:
>>
>>> You end up with two ignore files, probably the same rules in both
>> Far worse is the likelihood that multiple locations for the same
>> information will get out of sync. You will then have different programs
>> getting different sets of ignore rules when reading the same branch.
>>
>> This is what the “Don't Repeat Yourself (DRY)” principle is designed to
>> avoid <URL:http://c2.com/cgi/wiki?DontRepeatYourself>.

+1 on applying DRY here.

> Amen to that. Would it be so terrible to keep .bzrignore as a legacy
> special case forever (and never implement .bzrmeta/ignore)?

I think moving towards a consistent design is the best idea, though
timing is tricky. I'd like to see Bazaar 2.1 and later support
.bzrmeta/ignore *or* .bzrignore, i.e. 'bzr add' and 'bzr check' should
complain if both are found.

Practically, teams/communities tend to recommend a minimum version of
tools and only rely on new features once those minimum versions change.
Once a project says "bzr 2.1.0 is the minimum", then they can safely
rename .bzrignore to .bzrmeta/ignore and all should be well.

Ian C.