From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Git List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH v2 1/3] gitfaq: add documentation on proxies
Date: Mon, 08 Nov 2021 13:24:45 -0800 [thread overview]
Message-ID: <xmqqbl2utk6a.fsf@gitster.g> (raw)
In-Reply-To: <YYiDGhkaaQq7gpLK@camp.crustytoothpaste.net> (brian m. carlson's message of "Mon, 8 Nov 2021 01:53:30 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> I realize this sounds redundant, but I'm trying to avoid the situation
> where people say, "I'm not _tampering_ with it, since I'm authorized to
> do this by the company. I'm just modifying it to remove this
> inappropriate content/malware/data leak."
It might be a good strategy to educate users by leaving a deliberate
hole to let them quibble with such an excuse. When it comes to
on-the-wire protocol, their management do not have authority to
grant them right to tamper with the data and that is not limited to
Git.
next prev parent reply other threads:[~2021-11-08 21:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 22:55 [PATCH v2 0/3] Additional FAQ entries brian m. carlson
2021-11-07 22:55 ` [PATCH v2 1/3] gitfaq: add documentation on proxies brian m. carlson
2021-11-07 23:27 ` Eric Sunshine
2021-11-08 1:53 ` brian m. carlson
2021-11-08 21:24 ` Junio C Hamano [this message]
2022-01-04 13:40 ` Johannes Schindelin
2021-11-07 22:55 ` [PATCH v2 2/3] gitfaq: give advice on using eol attribute in gitattributes brian m. carlson
2021-11-07 23:48 ` Eric Sunshine
2021-11-08 2:09 ` brian m. carlson
2021-11-07 22:55 ` [PATCH v2 3/3] gitfaq: add entry about syncing working trees brian m. carlson
2021-11-08 0:12 ` Eric Sunshine
2021-11-08 22:09 ` Junio C Hamano
2021-11-09 0:10 ` Junio C Hamano
2021-11-14 23:40 ` brian m. carlson
[not found] ` <YYmmBMkwy6bpVpzI@camp.crustytoothpaste.net>
2021-11-09 0:02 ` Eric Sunshine
2021-11-08 0:16 ` [PATCH v2 0/3] Additional FAQ entries Eric Sunshine
2022-01-04 13:53 ` Johannes Schindelin
2022-01-04 13:54 ` Johannes Schindelin
2022-01-06 1:58 ` 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=xmqqbl2utk6a.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bagasdotme@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).