I'm working on a client project, where everything is developed in
Windows, and perforce is the official SCM. All the files use crlf line
endings.
I'm trying to use msysgit for my personal SCM, and git-p4 to sync with
perforce.
The problem I'm running into is that after
git p4 clone /perforce/path@all proj
all the files in the working directory are converted to lf line endings,
which I'd like to avoid.
I tracked it down to at some point git-p4 executes what essentially
amounts to
p4 -G print /path/to/file#rev
in order to get the content of a revision. When I try to run that
manually from the msysgit bash, the file content returned has all
the line endings converted to lf.
However, if I try to run without "-G", i.e.
p4 print /path/to/file#rev
The content returned has all the original crlf endings left intact.
I know this looks like a p4 issue, but I just wanted to ask other
git-p4 users out there whether you have run into this, and how you
dealt with it.
Thanks.
--
Jing Xue
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
