Re: [PATCH v2 1/3] gitfaq: add documentation on proxies

> I've seen this come up on the mailing list a couple times recently,
> though I haven't really followed along and don't use Git through an
> SSH proxy, thus I did have to go do some reading to understand what
> this is talking about. Perhaps people searching out this FAQ entry
> will already have sufficient context to understand what this is
> saying, so maybe no additional context is needed here. However, I was
> wondering if it might make sense for this to give a bit of reason
> explaining _why_ these tools need to be configured to not exit
> immediately upon EOF. As it stands now, this solution is a black box;
> it will work but people won't understand why. Perhaps that doesn't
> matter since most people consulting a FAQ like this probably just want
> to get the thing working and don't care about the underlying details.
> Then again, if the underlying reason is made more readily apparent,
> maybe this knowledge can become more widespread.

> "modify, tamper with, change" sounds like it came from the Department
> of Redundancy Department. I like the sound of "tamper with" since the
> image it conveys feels quite suitable here. Perhaps this could be
> simplified to:
> 
>    The proxy cannot tamper with or buffer the...