2 messages in com.perforce.perforce-user[p4] Content trigger bug?| From | Sent On | Attachments |
|---|---|---|
| Todd Short (tshort) | 26 Apr 2005 09:00 | |
| Jan Bakmann Kristiansen | 27 Apr 2005 00:51 |
| Subject: | [p4] Content trigger bug? |
|---|---|
| From: | Jan Bakmann Kristiansen (Jan....@csr.com) |
| Date: | 04/27/2005 12:51:56 AM |
| List: | com.perforce.perforce-user |
It's a bug.
I have reported it, but Perforce did not know when it would be solved, so please report it in order to get it solved as soon as possible.
If somebody has a good work-around I would very much like to hear about it. Perforce support suggested to change the file permission behind the "back" of perforce, but I don't find that solution usefull eventhough it solves the problem.
-Jan Kristiansen
-----Original Message----- From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Todd Short (tshort) Sent: 26. april 2005 18:01 To: perforce-user at perforce.com Subject: [p4] Content trigger bug?
I've been playing with triggers, and noticed that when using a 'content' trigger that purposely fails, the file(s) become read-only on the client.
Anyone else notice this? Bug?
Client/server: 2004.2
-- -Todd Short // tshort at cisco.com // "One if by land, two if by sea, three if by the Internet."
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user
To report this email as spam click https://www.mailcontrol.com/sr/FDsF4DbjAC6UYF42BS9q1kWjrCfLPcD J9Vdh4exE9UDkZ70bXASxQurKNToDHiBOIiM50BgiAYQh!RZaTLLnUUovN20TS TBM!GDfgygT8gyTnSvUxT+8ox!iYKU2z35EM0kMyXUazvU4yBCBrQrAJe9GcKV +XlmGP!qKvKuvrntRi4n4il6hAs12m6kN8gqSEHq9Ko5V+f3qtSS7yFNnUPrdS bGngRaA .
********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
**********************************************************************