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

[Ivey, William]

When we've had to do this, the developer usually branches based on
their client's state: @clientname (or head if that's more
appropriate), opens everything on the branch for edit then copies
their current files to the new branch in their workspace. They then
add any new files and reopen any deleted files for delete. Once
they're satisified that the new and old changelist and workspaces
are identical, they can revert the old one after copying the 
comments if any and revert unchanged files from the new one (or
wait until they're ready to submit).

The edits and adds are easy to handle, the deletes take a little 
more work, but there's nothing very complicated about it.

-Wm


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Troughton,
Robert


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