Diff and log options to ignore locks?
Brian de Alwis
bsd at cs.ubc.ca
Fri Jun 6 19:30:34 BST 2008
I often want to do a diff in a different shell when composing my
commit message. But both diff and log try to lock the branch. Is
there a way to tell diff + log to ignore the locks? (Perhaps I should
change my workflow.)
Also, with bzr 1.5, the reference manual says for 'break-lock':
You can get information on what locks are open via the 'bzr info'
command
But, doing 'bzr info' from a locked repository (from the
aforementioned commit) produces:
$ bzr info
bzr: ERROR: Could not acquire lock "[Errno 35] Resource temporarily
unavailable"
/usr/pkg/lib/python2.4/site-packages/bzrlib/lock.py:79: UserWarning:
lock on <open file u'/Users/bsd/NECTAR/GT-dev/gt-autoreconnect/.bzr/
checkout/dirstate', mode 'rb' at 0x12b3b60> not released
warn("lock on %r not released" % self.f)
Brian.
--
Brian de Alwis | Software Practices Lab | UBC | http://www.cs.ubc.ca/~bsd/
"Amusement to an observing mind is study." - Benjamin Disraeli
More information about the bazaar
mailing list