[p4] Difference between "edit" and "add" in "p4 opened" output?

[Strelzyk, Stephen]

If you are branching and then editing the files before the first submit
the files will always say add.  The process that we follow for branching
if to perform the p4 integ followed by the p4 submit.  You will have a
bunch of Rev 1's that are identical, but we like that approach because
it becomes obvious as to where the version originated from.  Open your
files that you need to change with p4 edit and then finish up with the
final p4 submit.  

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Roy Smith
Sent: Sunday, July 29, 2007 10:34 AM
To: Perforce Users Mailing List
Subject: [p4] Difference between "edit" and "add" in "p4 opened" output?

I'm moving a directory from one part of my source tree to another.  I  
did:

p4 integ foo/... bar/foo/...
p4 delete foo/...

As expected, the files in the new location show up with "p4 opened"  
as "branch default change (text)".

Before I submit, I need to edit some of the files to change #include  
paths.  I use the emacs integration, so on each of those files, I did  
"c-x p e" (p4-edit).  When I look at any of those edited files with  
"p4 opened", they show up as "add default change (ktext)".  I  
expected them to be listed as "edit", not "add".

Should I be worried?  My concern is that they will show up as new  
files, and I'll lose the revision history going back to their old  
locations in the source tree.

-------------------
Roy Smith <smith_roy at emc.com>
Software Guy, EMC Common Management Group
44 South Broadway, 7th floor
White Plains, NY 10601
(914) 580-3427
AIM: roysmith649

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