Say we have trunk codeline with two project branches.
A developer renames a file in one of the project branches (using the
P4win rename command) and then integrates that branch into the trunk.
A different developer edits the contents of that same file in the other
branch - the file there still has the old name.
That's definitely a huge problem for us. We are (unfortunately) working
with multiple branches, and I'd like people to rename files often as we
refactor classes. Unfortunately, because of that limitation, we're pretty
much never renaming files anymore.
If we have to rename something, we usually send out a team-wide email
verifying that nobody is using those files (or used, or will use those
files any time soon), and go ahead with the renaming.
When I talked to the P4 developers this summer at Siggraph, they said they
were working on a solution, so I'm keeping my fingers crossed we'll see
that problem go away sometime in 2005.
It really is a huge impediment for us.
--Noel
3 messages in com.perforce.perforce-user[p4] Impact of Renaming on Integration