@matheusbsbs / matheus-bagliano / commits / bb5ea62d80

git p4: remove unreachable windows \r\n conversion code

Replacing \r\n with \n on windows was added in c1f9197 (Replace \r\n with \n when importing from p4 on Windows, 2007-05-24), to work around an oddity with "p4 print" on windows. Text files are printed with "\r\r\n" endings, regardless of whether they were created on unix or windows, and regardless of the client LineEnd setting. As of d2c6dd3 (use p4CmdList() to get file contents in Python dicts. This is more robust., 2007-05-23), git-p4 uses "p4 -G print", which generates files in a raw format. As the native line ending format if p4 is \n, there will be no \r\n in the raw text. Actually, it is possible to generate a text file so that the p4 representation includes embedded \r\n, even though this is not normal on either windows or unix. In that case the code would have mistakenly stripped them out, but now they will be left intact. More information on how p4 deals with line endings is here: http://kb.perforce.com/article/63 Signed-off-by: Pete Wyckoff <pw@padd.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Pete Wyckoff committed Jan 26, 2013 at 22:11 UTC bb5ea62d80313f6fd37f3f3c214c78feb34036f9

1 file changed -9

git-p4.py

-9

@@ -2134,15 +2134,6 @@ class P4Sync(Command, P4UserMap):

2134 print "\nIgnoring apple filetype file %s" % file['depotFile']

2135 return

2136

2137 - # Perhaps windows wants unicode, utf16 newlines translated too;

2138 - # but this is not doing it.

2139 - if self.isWindows and type_base == "text":

2140 - mangled = []

2141 - for data in contents:

2142 - data = data.replace("\r\n", "\n")

2143 - mangled.append(data)

2144 - contents = mangled

2145 -

2137 # Note that we do not try to de-mangle keywords on utf16 files,

2138 # even though in theory somebody may want that.

2139 pattern = p4_keywords_regexp_for_type(type_base, type_mods)