[p4] perforce vs. subversion

[Weintraub, David]

If you're on Unix:

$ find . -type f | p4 -x - files > /dev/null

If you're on Windows:

$ dir /B/A-D/S | p4 -x - files > NUL

The error output will show files that are local, but not in Perforce. A
bit fancier on Unix:

$ $ (find . -type f | p4 -x - files > /dev/null) 2>&1 | sed 's/ - .*$//'

This moves the files to STDOUT and removes the error message. That way,
you could use this as an input to another pipe.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of
Ken.Williams at thomson.com
Sent: Thursday, May 04, 2006 3:18 PM
To: Patrick.Bennett at inin.com; noah at ncircle.com; sroberts at bycast.com
Cc: perforce-user at perforce.com
Subject: Re: [p4] perforce vs. subversion

The -sa flag finds "Opened files that are different from the revision in
the depot, or missing."  I'm talking about local files that don't exist
in the depot.

 -Ken


 

> -----Original Message-----
> From: Bennett, Patrick [mailto:Patrick.Bennett at inin.com]
> Sent: Thursday, May 04, 2006 12:24 PM
> To: Williams, Ken (TLR Corp); noah at ncircle.com; sroberts at bycast.com
> Cc: perforce-user at perforce.com
> Subject: RE: [p4] perforce vs. subversion
> 
> p4 diff -sa ... 
> 
> > -----Original Message-----
> > From: perforce-user-bounces at perforce.com
> > [mailto:perforce-user-bounces at perforce.com] On Behalf Of 
> > Ken.Williams at thomson.com
> > Sent: Thursday, May 04, 2006 10:46 AM
> > To: noah at ncircle.com; sroberts at bycast.com
> > Cc: perforce-user at perforce.com
> > Subject: Re: [p4] perforce vs. subversion
> > 
> > I think one big one for a lot of people is to easily know what files

> > are "new" without actually adding them.  You don't have to use a 
> > CVS-style workflow to want that one.
> 
> 
> 
> 
> 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user