Hi all,
first of all, many thanks to everyone involved for their release work on 0.47 and the conversion of the repository to bzr! Good job!!
I just did my first cautios steps in playing with the new repo and bzr, and I was wondering whether it's really a good idea to put the file .bzrignore under version control. For after checking out trunk and compiling, I've ended up with a lot of files that are neither under version control nor currently present in .bzrignore and thus totally clutter the output of 'bzr status'. But if I add them to .bzrignore then I need to be careful not accidentally commit the file (because surely we don't want every developer to add more stuff to .bzrignore which may only be relevant to his/her specific checkout). So wouldn't it be better to not provide a 'central' .bzrignore file and let the developers create local ones instead if desired?
Thanks for any opinions, Max
On Sun, 29 Nov 2009 13:19:07 +0000 Maximilian Albert <maximilian.albert@...1439...> wrote:
I was wondering whether it's really a good idea to put the file .bzrignore under version control.
It's put under VC automatically by the `bzr ignore` command.
I think it should probably be that way to adhere to standard practice.
So I don't know if there is any mechanism to deal with your problem - perhaps some of the stuff you're seeing could be ignored by everyone, at least for VC purposes? If a file should not be in VC, I can't imagine it hurts to have it in .bzrignore.
Cheers -Terry
On Sun, 2009-11-29 at 13:19 +0000, Maximilian Albert wrote:
I just did my first cautios steps in playing with the new repo and bzr, and I was wondering whether it's really a good idea to put the file .bzrignore under version control. For after checking out trunk and compiling, I've ended up with a lot of files that are neither under version control nor currently present in .bzrignore and thus totally clutter the output of 'bzr status'. But if I add them to ..bzrignore then I need to be careful not accidentally commit the file (because surely we don't want every developer to add more stuff to ..bzrignore which may only be relevant to his/her specific checkout). So wouldn't it be better to not provide a 'central' .bzrignore file and let the developers create local ones instead if desired?
I think that there should be one under version control. But, you can also add local entries to your own Bazaar directory if you'd like. It's in ~/.bazaar/ignore
--Ted
participants (3)
-
Maximilian Albert -
Ted Gould -
Terry Brown