[p4] Detecting files that were modified but not checked out

Kevin Sikes kevinsikes at sbcglobal.net
Fri May 19 15:08:50 PDT 2006


In P4Win, this equivalent feature is executed via File - More - Check
Consistency, which gives output like this:
STATUS:  Executing p4 diff -sd C:\depot\foo\...
  ===>   There are no missing files in the selected folders.
STATUS:  Executing p4 diff -se C:\depot\foo\...
  ===>   There are no unopened selected files that differ from the depot
version.

Sincerely,
Kevin Sikes

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Paul Goffin
Sent: Friday, May 19, 2006 3:01 PM
To: Edil Cadenas; perforce-user at perforce.com
Subject: Re: [p4] Detecting files that were modified but not checked out

p4 diff -se ...

(There's an equivalent in both GUIs).

Paul.

-----Original Message-----
From:	Edil Cadenas [mailto:Edil.Cadenas at ktd-kyocera.com]
Sent:	Fri 19/05/2006 18:07
To:	perforce-user at perforce.com
Cc:	
Subject:	[p4] Detecting files that were modified but not checked out

Does anyone know if there is a way to find all files in the workspace
that have been modified without being checked out?  We use certain
scripts that require files to be modified without being checked out so
what our users do is to change the attributes of workspace files to
writeable.

 

In VSS, there is a tool to find these files that were modified but were
not checked out.  ClearCase also detects these files.  Does anyone know
if such functionality also exists in Perforce?

 

With much thanks,

Edil Cadenas



 

_______________________________________________
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