This series introduces some additional Git FAQ entries on various topics. They are all things I've seen in my professional life or on Stack Overflow, so I've written documentation. There were some suggestions in the past that the text "modify, tamper with, or buffer" might be somewhat redundant, but I've chosen to keep the text as it is to avoid arguments like, "Well, buffering the entire request or response isn't really modifying it, so Git should just work in that situation," when we already know that doesn't work. Changes from v2 (partial): * Add documentation on proxies to the configuration documentation as well. * Mention some security problems that are known to occur with TLS MITM proxies. This mirrors the similar Git LFS documentation. * Provide a documentation example about how to use proxies with SSH. * Recommend running a `git fsck` after syncing with rsync. Changes from v1: * Drop the monorepo patch for now; I want to revise it further. * Reorder the working tree patch to place more warnings up front. * Mention core.gitproxy and socat. * Rephrase text in the EOL entry to read correctly and be easier to understand. * Improve the commit message for the working tree FAQ entry to make it clearer that users wish to transfer uncommitted changes. brian m. carlson (4): gitfaq: add documentation on proxies gitfaq: give advice on using eol attribute in gitattributes gitfaq: add entry about syncing working trees doc: mention that proxies must be completely transparent Documentation/config/http.txt | 5 ++ Documentation/gitfaq.txt | 105 ++++++++++++++++++++++++++++++++-- 2 files changed, 104 insertions(+), 6 deletions(-)
