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

[Jeff A. Bowles]

Also, in P4V...

When you have completely empty changelists, try this: "select top  
folder in your workspace using the workspace tab view, then right- 
click. Select 'mark for add'. Watch."

It'll recursively walk through your directory tree, adding the files  
that aren't there already. Be careful - you might want to explicitly  
MAP OUT things like .class files and .lib files before you do this,  
or remove them from the changelist that results.   (Then submit the  
changelist.)

It's sorta slick.

Of course, from command-line there's the "p4unknown" script in Perl,  
in Python, and in Ruby. It can be found in //guest/jeff_bowles/ 
scripts/... on the Public Depot. (It makes two (2) calls to 'p4',  
total - one to get the client name, another to retrieve the list of  
what's mapped to the workspace.)

	-Jeff Bowles
	Perforce Consulting Partner

On Jun 1, 2006, at 8:46 AM, Taylor Brown wrote:

> Thank you Shawn for the quick reply.  I'll check them both out.
>
>
>
> Cheers,
>
>
>
>     Taylor
>
>
>
> ________________________________
>
> From: Shawn Hladky [mailto:p4shawn at gmail.com]
> Sent: Thursday, June 01, 2006 10:39 AM
> 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