[p4] Perforce triggers

Todd Short (tshort) tshort at cisco.com
Wed Jul 12 07:31:50 PDT 2006


We've experinced the same thing when checking contents for certain
things. I thought I had reported this, but it won't hurt to have
another.

--
-Todd Short
// tshort at cisco.com
// "One if by land, two if by sea, three if by the Internet."
 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
> Sent: Wednesday, July 12, 2006 9:47 AM
> To: Knight, Steve
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Perforce triggers
> 
> Leaving it locked in Perforce happens when the submission 
> fails. Leaving 
> it read-only seems like a bug to me unless it was from an 
> integration. 
> I'd report this to support. Be sure to include your version 
> information 
> for both client and server.
> 
> Steve
> 
> Knight, Steve wrote:
> > Hello,
> >
> > Much to the annoyance of some of the developers at our 
> organisation I've
> > added certain code format checks into a Perforce 
> change-content trigger.
> > This seems to work very well.
> >
> > However, one of the side affects is that should the 
> submission fail it
> > will leave the file locked and read only on the client.     
> So the file
> > then has to be at the very least chmod'd and possibly unlocked too.
> > Even the people who support the spirit of what I'm trying 
> to do aren't
> > too keen on this second aspect.
> >
> > Is there something I'm doing wrong or is it a bug?   (I 
> couldn't find
> > anything relevant in the Tech Notes ...)
> >
> > Thanks
> >
> > Steve
> >
> > -----
> > This message may contain confidential, proprietary, or 
> legally privileged information.  No confidentiality or 
> privilege is waived by any transmission to an unintended 
> recipient.  If you are not an intended recipient, please 
> notify the sender and delete this message immediately.  Any 
> views expressed in this message are those of the sender, not 
> those of KBC Financial Products or any affiliate thereof. 
> >
> > This message does not create any obligation, contractual or 
> otherwise, on the part of any such entity.  It is not an 
> offer (or solicitation of an offer) of, or a recommendation 
> to buy or sell, any financial product.  Any prices or other 
> values included in this message are indicative only, and do 
> not necessarily represent current market prices, the prices 
> at which any KBC entity would enter into a transaction or the 
> prices at which similar transactions may be carried on that 
> entity's own books.   The information contained in this 
> message is provided "as is", without representations or 
> warranties, express or implied, of any kind.  Past 
> performance is not indicative of future returns.  
> >
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >   
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 




More information about the perforce-user mailing list