[p4] A tool to list all files that haven't been added

Rick Cameron Rick.Cameron at businessobjects.com
Thu Jun 1 10:29:14 PDT 2006


I don't know p4v very well - can you tell me how to use the folder diff
to identify local source files that are not in the depot?

When I use Tools | Diff I have to put references to locations of the
same type (i.e. two depot paths, or two local paths) in the dialog. It
doesn't appear to allow me to compare a local directory with a depot
folder.

This is with p4v 2005.2/94595.

Cheers

- rick

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Shawn Hladky
Sent: Thursday, 1 June 2006 8:39
To: Taylor Brown
Cc: perforce-user at perforce.com
Subject: Re: [p4] A tool to list all files that haven't been added

p4v's folder diff will do this.  So will araxis w/ the Perforce plugin.

On 6/1/06, Taylor Brown <tbrown at ncsoft.com> wrote:
>
>
> Is there a GUI tool out there (or a way to do this in the Perforce 
> GUIs) that allows me to see, at a glance, the difference between my 
> perforce depot and my local drive?  In particular, I need an easy way 
> to see which files I have forgotten to add to Perforce.  When you all 
> need to guarantee that your checkin won't miss any new files, do you 
> just recursively add files that match particular wildcards? For
example:
> Recursiveadd.bat *.cpp
> Recursiveadd.bat *.h
> ...
>
> This could work, but I'm still worried it could miss the oddly named 
> new file.
>
> I'd love to have a tool to recommend to our devs as a best practice 
> before they do their checkin.  I am guilty of performing a checkin, 
> syncing to a clean branch, testing, and then adding the files I
forgot.
> Although I work in my own branch, I still don't like the idea that I'm

> breaking the branch until I get all my files checked in.  I'd rather 
> it be more atomic.
>
> What I _really_ want (and now I'm dreaming) is a Beyond Compare plugin

> where one side is my local file system and the other is my Perforce 
> depot...Now THAT would be a tool.
>
> Many thanks for any advice or assistance,
>
>    Taylor
>
> _______________________________________________
> 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