[p4] FW: Identifying binary files

todd.benham@kodak.com todd.benham at kodak.com
Tue Jan 15 06:54:51 PST 2008


No, that's not the answer I was hoping for. Ick, but thanks.

That does work, however, for locating binaries in the depot.

What methods are available to help prevent changes to binaries in separate
branches? 
I know that someone is going want to merge changes in a binary made in the
wrong branch.
Do you have a setup that prevents branching of un-mergeable binaries?

Here is my list of ideas (but I don't like the choices):

1) do not put binaries in depot area that need to branch
   (i.e. separate /depot/src & /depot/bin right at the top)
2) in branch specs exclude binary in branch by extension (*.doc, *.bin,
...)
3) have a policy that says do not edit binaries in branches that merge
(left unenforced)
4) use triggers ???



Todd  


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Robert Cowham
Sent: Monday, January 14, 2008 4:52 PM
To: perforce-user at perforce.com
Subject: [p4] FW: Identifying binary files


Yes via command line by piping to grep or findstr (or via simple
ruby/python/perl script).

Commands such as p4 fstat as opposed to p4 files, or p4 -ztag files can
sometimes be useful. 

(On windows with Unxutils installed)
p4 files //... | grep "\(.*binary.*\)$"
or
p4 fstat //... | grep -2 "headType.*binary" | grep depotFile

You might want to ignore deleted files - exercise for reader!

For GUIs it's a case of wrapping the above in a custom tool.

This may not have been the answer you were hoping for :)

> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> todd.benham at kodak.com
> Sent: 14 January 2008 18:20
> To: perforce-user at perforce.com
> Subject: [p4] Identifying binary files
> 
> Is there a way to list only binary type files in the depot? Such as p4 
> files //depot/...(binary)
>  
>  
> Related but different ...
>  
> Is there a way to exclude binary files in a branch spec?
> Such as -//depot/...(binary) //depot/...(binary)
>  
>  
> I am not finding a way to do this.
_______________________________________________
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