[p4] developer branches

[Weintraub, David]

Haven't really worked with the plug in, so I really can't say. The
P4/VisualStudio integration can't handle it, but it can't even do
branching or merging.

The problem has to do with reverting unchanged files. Normally, a "p4
revert -a" would work (and both P4V and p4win have similar commands.
However, "p4 revert -a" won't revert an unchanged file that is involved
with an integration.

To get around the problem, you go to the "Tools" menu and add a command
to the "Tools" directory. In P4V, you set it up like this:

Application: C:\Program Files\Perforce\p4.exe

Arguments: diff -sr | p4 -x revert

Run tool in terminal window: (checked)
Refresh P4V upon completion: (checked)

I have a Word document in the Perforce public archive
<http://snipurl.com/p4merge> that I wrote for users describing branching
and merging in Perforce. It's a long document (current version is 28
pages), but it is about 80% screen shots. The last 9 pages (6.2 Using
P4V for Integrating Convergent Branches) covers setting up P4V for the
process and how to  copy a convergent child branch back to the parent
branch in eight steps. Don't let the 9 pages fool you. It's about 1/2
page of text and 8 1/2 pages of step-by-step screen shots).

-----Original Message-----
From: Betsill, Marilyn [mailto:betsillm at TEOCO.com] 
Sent: Tuesday, November 21, 2006 2:03 PM
To: Rick Macdonald; Weintraub, David
Cc: perforce-user at perforce.com
Subject: RE: [p4] developer branches

Thanks to all for the info on developer branches.

David-

You mentioned that it's "pretty easy" to add a step that supports merge
down/copy up to p4v and p4win.  How would you do this?  Also, does
anyone know whether a similar change could be made in the eclipse
(p4wsad) plug-in?

TIA,
Marilyn

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Rick Macdonald
Sent: Wednesday, November 15, 2006 2:59 PM
To: Weintraub, David
Cc: perforce-user at perforce.com
Subject: Re: [p4] developer branches

David -

That should be "Merge _down_, Copy _up_" !

...RickM...

Weintraub, David wrote:
> We use private developer branches on quite a few occasions. Mainly, so

> the build doesn't break while long term changes are taking place.
Using
> private development branches is not the standard way Perforce is used,

> but Perforce does a good job handling the situation if you follow
Laura
> Wingerd's "merge up/copy down" approach. There's a paper on this 
> technique at <http://snipurl.com/perforce>.
>
> There is a minor issue in using this "merge up/copy down" method if
you
> use the P4V or p4win programs because there's one step that's not 
> directly built into those GUI's menu system. However, its pretty easy
to
> add this step to these programs, so that's not really a show stopper.
>
> I haven't used the Eclipse plug-in for Perforce, but apparently it is 
> very good.
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Betsill, 
> Marilyn
> Sent: Wednesday, November 15, 2006 10:39 AM
> To: perforce-user at perforce.com
> Subject: [p4] developer branches
>
> Has anyone implemented developer-private branches?  
>
>  
>
> We have a limited need for them (1-2 devs out of about 10).  We would 
> use a dev-private branch when work on a bug fix or enhancement may
take
> several weeks, and a developer needs to minimize the impact of losing 
> his workspace (due to a local disk problem, for example). Builds would

> break if the changes were checked in incrementally to the shared 
> 'Working' branch.
>
>  
>
> I'm evaluating Perforce/p4wsad as a possible replacement for 
> CVS/eclipse; thanks in advance for your help.
>
>  
>
> Marilyn Betsill
>
> TEOCO Corporation
>
> Fairfax, VA  22033
>
> _______________________________________________
> 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
>
>   

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