[p4] P4Win vs P4V

Shawn Hladky p4shawn at gmail.com
Wed Jul 5 12:29:05 PDT 2006


1) Check Consistency
2) Command Prompt...
3) Explore...

2 & 3 are simple to add as custom tools.

On 7/5/06, Pavloff, Alex (IE) @ SONOMAEO <alex.pavloff at l-3com.com> wrote:
>
>
> P4Win.
>
> Features not in P4V (and may never be, seeing as how P4V is
> cross-platform)
>
> 1) Check Consistency
> 2) Command Prompt...
> 3) Explore...
>
>         -Alex
>
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Marshall, Tony
> [IT]
> Sent: Wednesday, July 05, 2006 1:52 AM
> To: perforce-user at perforce.com
> Subject: [p4] P4Win vs P4V
>
> What do Windows users tend to use most - P4Win or P4V? I thought that
> since P4V is cross-platform, it would be the strategic direction that
> Perforce would go when developing the product. So I recommended that we
> use it in our team before evaluating both of them. However, I'm finding
> that P4Win has useful features that P4V (2005.2) doesn't - e.g. Safe
> automatice resolve, linking submitted changelists to jobs, viewing
> workspace files not in the depot. That's really annoying!
>
> _______________________________________________
> 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