Dangerous new server status for deleted files

Hi,

Our new Perforce server (P4D/NTX64/2009.2/228098 2009/12/16) seems to be 
giving out 'move/delete' instead of the old 'delete' status for files 
that are moved within the repo. Attached is the simple patch to fix it. 
(By the way: How do you "sign off" a patch?) This is urgent, as it will 
corrupt git repos trying to track a Perforce depot.

Thanks,

PKE.

-- 
Pål-Kristian Engstad (engstad@naughtydog.com), 
Lead Graphics & Engine Programmer,
Naughty Dog, Inc., 1601 Cloverfield Blvd, 6000 North,
Santa Monica, CA 90404, USA. Ph.: (310) 633-9112.

"Emacs would be a far better OS if it was shipped with 
 a halfway-decent text editor." -- Slashdot, Dec 13. 2005.

On Wednesday 20 January 2010, Pal-Kristian Engstad wrote:

Our new Perforce server (P4D/NTX64/2009.2/228098 2009/12/16) seems to be
giving out 'move/delete' instead of the old 'delete' status for files
that are moved within the repo. Attached is the simple patch to fix it.
(By the way: How do you "sign off" a patch?) This is urgent, as it will
corrupt git repos trying to track a Perforce depot.

Hi, and welcome to the Git community.

The patch itself may be fine, but you should probably read 
Documentation/SubmittingPatches for hints on the customs of this list. For 
example: We prefer patches _inline_ in the mail, so that it's easier to 
review and comment on them. The Documentation/SubmittingPatches also 
explains what is meant by a sign-off, and how to sign-off your patches.


Have fun! :)

...Johan

-- 
Johan Herland, [off-list ref]
www.herland.net