gopher: fix test case line endings

Patches over email very easily lose CRLF line endings in files otherwise
LF-only so I had to put them back where needed.
This commit is contained in:
Daniel Stenberg 2010-08-24 23:15:59 +02:00
Родитель cb64c987a0
Коммит 53151db167
4 изменённых файлов: 17 добавлений и 17 удалений

Просмотреть файл

@ -11,9 +11,9 @@ INDEX
# Server-side
<reply>
<datacheck>
iMenu results error.host 1
0Selector /bar bar.foo.invalid 70
.
iMenu results error.host 1
0Selector /bar bar.foo.invalid 70
.
</datacheck>
</reply>
@ -34,7 +34,7 @@ gopher://%HOSTIP:%GOPHERPORT
# Verify data after the test has been "shot"
<verify>
<protocol>
</protocol>
</verify>
</testcase>

Просмотреть файл

@ -11,9 +11,9 @@ SELECTOR
# Server-side
<reply>
<datacheck>
iMenu results error.host 1
0Selector /selector/SELECTOR /bar bar.foo.invalid 70
.
iMenu results error.host 1
0Selector /selector/SELECTOR /bar bar.foo.invalid 70
.
</datacheck>
</reply>
@ -34,7 +34,7 @@ gopher://%HOSTIP:%GOPHERPORT/1/selector/SELECTOR
# Verify data after the test has been "shot"
<verify>
<protocol>
/selector/SELECTOR
/selector/SELECTOR
</protocol>
</verify>
</testcase>

Просмотреть файл

@ -11,10 +11,10 @@ QUERY
# Server-side
<reply>
<datacheck>
iSearch results error.host 1
0Query query succeeded /foo foo.bar.invalid 70
0Selector /the/search/engine /bar bar.foo.invalid 70
.
iSearch results error.host 1
0Query query succeeded /foo foo.bar.invalid 70
0Selector /the/search/engine /bar bar.foo.invalid 70
.
</datacheck>
</reply>
@ -35,7 +35,7 @@ gopher://%HOSTIP:%GOPHERPORT/7/the/search/engine?query%20succeeded
# Verify data after the test has been "shot"
<verify>
<protocol>
/the/search/engine query succeeded
/the/search/engine query succeeded
</protocol>
</verify>
</testcase>

Просмотреть файл

@ -12,9 +12,9 @@ INDEX
# Server-side
<reply>
<datacheck>
iMenu results error.host 1
0Selector /bar bar.foo.invalid 70
.
iMenu results error.host 1
0Selector /bar bar.foo.invalid 70
.
</datacheck>
</reply>
@ -35,7 +35,7 @@ Gopher IPv6 index
# Verify data after the test has been "shot"
<verify>
<protocol>
</protocol>
</verify>
</testcase>