ignored

[Martin Pool]

On Wed, 2005-04-13 at 12:53 +0100, Paul Jakma wrote:
> Hi,
> 
> I'm having problems with the ignore command and the ignore 
> functionality:
> 

> 1. the docs refer to an ignore command but it doesnt work

Yep :-)

There will be one when I (or someone else) writes it.  It should be
trivial.

We might want to help people with quoting problems.  Saying 

  $ bzr ignore *.class

will *seem* to do the right thing but actually won't match new files
added in the future.  We might insist on adding only one pattern at a
time, which will catch that.

  $ bzr ignore '*.class'

> 
> $ bzr ignore
> bzr: error: unknown command 'ignore'
> (see $HOME/.bzr.log for debug information)
> 
> 2. The docs refer to a .bzr-ignore file, but it appears the name is 
> actually .bzrignore :)

Thanks.

> 3. .bzrignore entries are recursive
> 
> This last one is a real killer. Say we have 'INSTALL' listed in the 
> .bzrignore file in the top-level directory of a project, because the 
> top-level INSTALL file will be provided by autoconf/automake, so the 
> INSTALL file in the top-level directory is (rightfully) ignored, 
> however, it also ignores subdir/INSTALL unfortunately..
> 
> How do i undo this?

You want

  ./INSTALL

Anything with a slash matches a whole path, not just a filename

> Further, this recursive it makes it *really* difficult to migrate 
> from CVS.

That's true.

>  It'd be much nicer to have .bzrignore files apply on a 
> per-directory basis: Better granularity, consequences are far easier 
> to understand as the scope is the more limited, the regexes/patterns 
> dont have to be as complex, etc.. Any additional tedium imposed by 
> per-dir ignore files is easily overcome with 'cp 
> ../existing-dir/.ignore-file ./' when adding directories ;)

I suppose we can have both.

But CVS ignores are rather baroque, so I'm not sure I want to promise
they can be totally supported.   I for one like the new system rather
better, partly because we can now do 'bzr add .' and ignore the right
things in subdirectories.

> This little niggle is a bit of an obstacle to me trying out bzr 
> further ;) - and i'd like to.
> 
> Having tinkered with GNU arch before: nice work on the UI, it's 
> actually understandable. Bravo. One nit: could 'bzr help' offer a 
> 'global options' category, or a 'help-options' command? :) Also, 
> per-command help dont list the options the command has, eg:
> 
> $ bzr help log
> Show log of this branch.
> 
> :todo: Options for utc; to show ids; to limit range; etc.
> 
> However, I know from 'bzr log' on the bzr archive that a --verbose 
> long-option was added :).

Yes, should do that.

> Anyway, looking very very promising. Nice work.

Thanks.

> Some people have a great ambition: to build something
> that will last, at least until they've finished building it.

How appropriate. :-)
-- 
Martin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050413/1e73d7e1/attachment.pgp