Geek asks and answers

Can a bazaar ignore a file that already exists in a branch?

On my local machine, the configurations are different from the test and production servers.

Every time I want to transfer my local code, it notices (Bazaar Explorer) that I edited the configuration file. Now I explicitly ignore this file with every commit. However, from time to time this happens incorrectly.

Using ignoring a branch or user does not solve the problem. The file is already in the trunk.

Someone has a good strategy, a workaround, or maybe the right parameter for this has been found.

Thank!

+3
source share
2 answers

. , , . , - :

bzr remove --keep conf.ini
bzr ignore conf.ini
cp conf.ini conf.sample.ini
<maybe edit the new sample to be generic>
bzr add conf.sample.ini
bzr ci -m "don't track the actual conf file any more"
+4

bzr commit exclude :

alias bzrcom = 'bzr commit --exclude =/path/to/your/config'

0

More articles:


All Articles