configured to always require exclusive locks, so may be a problem for
all revisions in some cases.
Signed-off-by: Danny Thomas
---
git-p4.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-p4.py b/git-p4.py
index 0682e61..ffba294 100755
--- a/git-p4.py
+++ b/git-p4.py
@@
Interesting. 'Implementing sitewide pessimistic locking with p4 typemap',
http://www.perforce.com/perforce/doc.current/manuals/p4sag/03_superuser.htm
l seems to suggest this is all that's needed. I believe we're using the
default configuration, the exclusive lock on all files behaviour was
research
Sounds good to me. I've got a couple of busy days coming up, but should
have time this week.
Danny
On 19/03/2013 19:23, "Pete Wyckoff" wrote:
>danny.tho...@blackboard.com wrote on Mon, 18 Mar 2013 09:26 -0400:
>> Interesting. 'Implementing sitewide pessimistic locking with p4
>>typemap',
>>
3 matches
Mail list logo