From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Eric Sunshine <sunshine@sunshineco.com>,
Derrick Stolee <stolee@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH v3 0/4] Additional FAQ entries
Date: Wed, 03 Jul 2024 18:25:43 -0700 [thread overview]
Message-ID: <xmqqh6d69cdk.fsf@gitster.g> (raw)
In-Reply-To: <20240704003818.750223-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Thu, 4 Jul 2024 00:38:14 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 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.
Just to help other readers:
v1
https://lore.kernel.org/git/20211020010624.675562-1-sandals@crustytoothpaste.net/
v2
https://lore.kernel.org/git/20211107225525.431138-1-sandals@crustytoothpaste.net/
are where the previous discussions are found.
> 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(-)
next prev parent reply other threads:[~2024-07-04 1:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 0:38 [PATCH v3 0/4] Additional FAQ entries brian m. carlson
2024-07-04 0:38 ` [PATCH v3 1/4] gitfaq: add documentation on proxies brian m. carlson
2024-07-04 0:38 ` [PATCH v3 2/4] gitfaq: give advice on using eol attribute in gitattributes brian m. carlson
2024-07-04 5:22 ` Junio C Hamano
2024-07-04 21:10 ` brian m. carlson
2024-07-04 0:38 ` [PATCH v3 3/4] gitfaq: add entry about syncing working trees brian m. carlson
2024-07-04 5:21 ` Junio C Hamano
2024-07-04 21:08 ` brian m. carlson
2024-07-06 5:50 ` Junio C Hamano
2024-07-04 0:38 ` [PATCH v3 4/4] doc: mention that proxies must be completely transparent brian m. carlson
2024-07-04 1:25 ` Junio C Hamano [this message]
2024-07-04 5:22 ` [PATCH v3 0/4] Additional FAQ entries Junio C Hamano
2024-07-04 21:23 ` brian m. carlson
2024-07-06 5:59 ` Junio C Hamano
2024-07-08 0:52 ` brian m. carlson
2024-07-06 6:47 ` Jeff King
2024-07-06 17:18 ` Junio C Hamano
2024-07-09 23:37 ` [PATCH v4 " brian m. carlson
2024-07-09 23:37 ` [PATCH v4 1/4] gitfaq: add documentation on proxies brian m. carlson
2024-07-09 23:37 ` [PATCH v4 2/4] gitfaq: give advice on using eol attribute in gitattributes brian m. carlson
2024-07-09 23:37 ` [PATCH v4 3/4] gitfaq: add entry about syncing working trees brian m. carlson
2024-07-09 23:37 ` [PATCH v4 4/4] doc: mention that proxies must be completely transparent brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh6d69cdk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=stolee@gmail.com \
--cc=sunshine@sunshineco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.