Ignore use case: explicit ignore necessary?

[Jo Vermeulen]

Op 18-apr-05 om 15:09 heeft Martin Pool het volgende geschreven:

> On Mon, 2005-04-18 at 14:50 +0200, Jo Vermeulen wrote:
>> Hello again :-)
>>
>> I was reading the "ignore" use case [1], and wondered if ignoring 
>> files
>> should be made explicit. As far as I know, darcs [2] for example only
>> adds explicitly, and ignores the rest. So .pyc files would be
>> automatically ignored. This is not very ideal if you just added a new
>> source file though. Although you probably *know* this file belongs in
>> the repository, so you won't likely forget to explicitly add it.
>>
>> I'm not sure what the best solution is, but it seems implicit ignoring
>> could save the user some time.
>>
>> [1] http://www.bazaar-ng.org/doc/use-cases.html#ignore-some-files
>> [2] http://abridgegame.org/darcs/
>
> I don't understand your question, but since bzr already works similarly
> to darcs maybe it already does what you want?

Mmm indeed it does :-) Sorry! Ignoring is only necessary when you don't 
want bzr status to get cluttered up with unknown files.

One thing I did notice was that .bzrignore is not "ignored" by default. 
The tutorial says:

The .bzrignore file should normally be versioned, so that new copies of 
the branch see the same patterns:

% bzr add .bzrignore
% bzr commit -m "Add ignore patterns"

I understand why it couldn't be part of .bzr/ because it would still 
have to be user-editable ofcourse (and .bzr/ should not be edited). But 
it seems like .bzrignore is not really part of the project itself. When 
converting a bazaar-ng repository to CVS for example, .bzrignore still 
turns up in the CVS version. But maybe that's "desired behavior" since 
converting this repository to bazaar-ng again would restore the 
patterns :-)

Sorry if I'm bringing up old discussions on this matter.

Cheers!

-- 
Jo Vermeulen <jo at lumumba.luc.ac.be>
http://lumumba.luc.ac.be/jo/