search

kumar-nitish / ratproxy

Automatically exported from code.google.com/p/ratproxy
0 stars 0 forks source link

Spelling errors #26

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. run aspell on the sources

What is the expected output?
no misspellings :)

What do you see instead?
a couple

What version of the product are you using?
svn tip (rev 12)

On what operating system?
Linux

Original issue reported on code.google.com by timel...@gmail.com on 24 Dec 2008 at 11:18

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by timel...@gmail.com on 24 Dec 2008 at 11:19

Attachments:

GoogleCodeExporter commented 8 years ago 
The first diff applies (with whitespace errors, but that probably isn't an 
issue):

$ git-apply ratproxy.diff 
ratproxy.diff:32: trailing whitespace.
     basic character distribution data, rule out patterns such as unix 
ratproxy.diff:63: trailing whitespace.
    that lead to subtle XSSes, and includes MIME type mismatches, charset 
ratproxy.diff:77: trailing whitespace.
Initiating ratproxy sessions is fairly straightforward, once an appropriate set 
ratproxy.diff:78: trailing whitespace.
of runtime options is decided upon. Please familiarize yourself with these 
ratproxy.diff:87: trailing whitespace.
  will also forgo any server certificate validation steps - so while interacting 
warning: 5 lines add whitespace errors.
$

The second diff does not apply for me:
$ git apply ratproxy2.diff 
ratproxy2.diff:10: trailing whitespace.
If you intend to run ratproxy on a different operating system, you may 
error: patch failed: README:2
error: README: patch does not apply
$ grep "If you intend to run ratroxy on" README
$

Original comment by steve.mi...@gmail.com on 11 Jun 2009 at 6:16