bzr diff requires lock
Bug #176905 reported by
Aidan Delaney
This bug report is a duplicate of:
Bug #98836: [MASTER] "OS locks must die" - dirstate file write locks exclude readers and limit portability.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
New
|
Undecided
|
Unassigned | ||
Bug Description
bzr diff requires a dirstate lock in order to proceed. Given that "diff" does not modify the codebase I don't see why it must acquire a lock. An attempt to grab a lock foils the following usecase: When writing the changelog entry for a revision I want to review the diff. However I can't run "bzr diff" during my "bzr ci" as checkin acquires the lock.
(I'm probably the words only fan of "tla make-log", based on the above use-case.)
Revision history for this message
| Alexander Belchenko (bialix) wrote Re: [Bug 176905] bzr diff requires lock | #1 |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
To post a comment you must log in.
Aidan Delaney пишет:
> Public bug reported:
>
> bzr diff requires a dirstate lock in order to proceed. Given that
> "diff" does not modify the codebase I don't see why it must acquire a
> lock. An attempt to grab a lock foils the following usecase: When
> writing the changelog entry for a revision I want to review the diff.
> However I can't run "bzr diff" during my "bzr ci" as checkin acquires
> the lock.
It's a known issue.
Try this:
bzr ci --show-diff