Problem with bzr without default ignore list.
Matthieu Moy
Matthieu.Moy at imag.fr
Mon Jul 10 16:03:57 BST 2006
Hi,
Since a few revisions, bzr has no default ignore list. Globally, I
find it to be a good thing, because the default is usually hard to
override.
However, I'm just encountering a problem that I don't know how to
solve cleanly.
DVC (Emacs interface) uses a file .tmp-bzr-log-edit.txt to save
intermediate log messages (and then commit with --file
.tmp-bzr-log-edit.txt, this is the equivalent of the ++log.blah of GNU
Arch).
Using the .tmp prefix, we got sure this file would be ignored, but
now, this files pops up in "bzr status".
DVC is one example, but "bzr shelve" has the same problem, and many
other bzr-related tools will also want to store hidden or temporary
files in the tree.
My suggestion is to re-enable a default ignore list, with just one
pattern in the default ignore list, like ".bzr-*", or maybe
".bzr-ignore-*" so that third-party applications can use
.bzr-<appname>-whatever for hidden files.
The other option is to have the application set up its own ignore list
when needed. This would be reasonable if a per-user ignore list is
implemented (then DVC would add itself to this list the first time).
Any opinion?
--
Matthieu
More information about the bazaar
mailing list