[p4] Moving a changelist across to a new branch?

[Rick Macdonald]

I'll take a stab at this.

I would create a branch not from the head revision, but the "have" 
revisions that he originally took out for edit (there may be later 
updates to these files).

- sync that branch to a fresh workspace,
- delete all the files
- copy in the files that he has been working on for two weeks
- follow TechNote #2 to resolve the edits, adds and deletes:
   http://kb.perforce.com/UserTasks/WorkingDisconnected
- at some point, any changes to the parent that occurred after the 
branch of the original "have" revisions will need to be integrated to 
this new branch and resolved. This step of course is normal "merge down 
/ copy up" activity.

Rick

Troughton, Robert wrote:
> Imagine a situation where a programmer has been working on a change
> that's turned out to be much bigger than he'd first expected... his
> changelist expands to, say, 100 changes, a mixture of adds, deletes and
> edits, and it looks like the changelist will get bigger still before
> he's finally able to check it in.
>
> So... after two weeks of work, he decides that he should've created a
> branch for his changed.
>
> Basically... how easy would it be to create that branch from the current
> "head" version on Perforce and to pull his changelist across to that
> branch instead?
>
> Sorry if I've explained this badly ... I hope the question makes some
> sense?
>
> Robert
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>