mark wrote:
> - * Compare with superrclass that uses SocketWrapper
> + * Compare with superclass that uses SocketWrapper
Fwiw, I finally posted my spelling scripts at https://github.com/jsoref/spelling
If you wanted to, you could have a script that did:
```sh
mv
Hi Mark,
re: https://bz.apache.org/bugzilla/show_bug.cgi?id=57129
This change seems significant enough that it merits mention in:
https://tomcat.apache.org/migration-8.html
I've inherited a number of tomcat7 servers which host quite a few
wars/exploded wars, and I'd love to move us forward to
A client of my employers wanted to know how much life our chosen
application hosting platform has left.
I found Mark's email [1] which suggested tomcat 6 eol [2]. That page says:
> The Apache Tomcat team announces that support for Apache Tomcat 6.0.x will
> end on 31 December 2016.
> Three
Rainer Jung wrote:
> the old spec states "The Reason-Phrase is intended to give a short textual
> description of the Status-Code.
> The ... Reason-Phrase is intended for the human user."
"human user" should be a pretty big clue that a UA should not be using
it to make any decisions.
Any UA that
Christopher Schultz wrote:
> I'm wondering what the wider community thinks about this change and
> whether or not we should consider reverting it for Tomcat 8.5.x.
Mark Thomas wrote:
> The root cause is non-specification compliant clients. I generally don't
> view specification non-compliance in
I can drop that, but please note that the spelling is listed as corrected in
the MIT key server. I really wonder how tomcat managed to corrupt it.
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional
https://github.com/jsoref/tomcat/commit/7c6bc40ac289ee7e7c9655c69a529f18afb5b92f
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
I can certainly squash. The reason I personally retain splits by misspelled
word is that it's easier to rebase / resolve conflicts when I can see what
word was misspelled.
Typically large projects prefer to have my changes split into a couple of
patches/PRs instead of as a single commit.
As
Hi,
I have a series of spelling fixes for Apache Tomcat [1].
If someone could suggest a preferred way to receive them, I'm happy to
split them up.
Some changes are more interesting than others (the change to KEYS is
interesting).
[1] https://github.com/jsoref/tomcat/commits/spelling
