Skip to content
← General

I suggest you ...

General

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Make the listlocks command use lock.conf configuration

Currently, the listlocks command doesn't use what's configured in the lock.conf, making it confusing when using an external lock server. See this thread for more info : http://www.plasticscm.net/index.php?/topic/2064-exclusive-checkout-in-dvcs-configuration/#entry13367.

6 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Olivier Groulx shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Max Pixel commented  ·   ·  Report

    While you're at it, might as well do the same for `cm unlock`. If I `cm unlock 168ffbb4-ef54-4ee4-af4d-0dfd97050b1b`, and that GUID exists in the repository `assets`, and `lock.conf` contains `rep:assets lockserver:ServerA:8084`, then I expect it to actually do something. Instead, it does nothing, because nothing is locked on my local server. I am required to run `cm unlock ServerA:8084 168ffbb4-ef54-4ee4-af4d-0dfd97050b1b`