I reset all the files to be lf. I also forced all the windows users
IDEs to use Unix endings. I haven't seen that error since then
Thanks for the assistance
On Thu, Apr 18, 2013 at 7:43 PM, Pete Wyckoff p...@padd.com wrote:
christopher.yee...@gmail.com wrote on Thu, 18 Apr 2013 11:24 -0500:
The issue is caused by the line endings. I retested the problem with a
different file and in this case, the error is caused by the line
endings of the file checked out in the perforce workspace being
win-style crlf, and the line endings of the file in the git repo being
unix style lf. (In this
christopher.yee...@gmail.com wrote on Thu, 18 Apr 2013 11:24 -0500:
The issue is caused by the line endings. I retested the problem with a
different file and in this case, the error is caused by the line
endings of the file checked out in the perforce workspace being
win-style crlf, and the
l...@diamand.org wrote on Thu, 11 Apr 2013 21:19 +0100:
Just a thought, but check the files that are failing to see if they've
got RCS keywords in them ($Id$, $File$, $Date$, etc). These cause all
sorts of nasty problems.
That's assuming it's definitely not a CRLF line ending problem on
I tried running git p4 submit on a repo that I've been running as an
interim bridge between git and perforce. Multiple people are using the
repo as a remote and its being periodically submitted back to
perforce.
It's been working mostly fine. Then one day out of the blue I get this
error. I can
Just a thought, but check the files that are failing to see if they've
got RCS keywords in them ($Id$, $File$, $Date$, etc). These cause all
sorts of nasty problems.
That's assuming it's definitely not a CRLF line ending problem on Windows.
On Thu, Apr 11, 2013 at 8:01 PM, Christopher Yee Mon
6 matches
Mail list logo
