From: Stefan Kangas <stefankangas@gmail.com>
To: Lin Jian <me@linj.tech>
Cc: 68810@debbugs.gnu.org
Subject: bug#68810: 29.1; Recommending setting transfer.fsckObjects of git to true is not necessary
Date: Tue, 30 Jan 2024 15:49:34 -0500 [thread overview]
Message-ID: <CADwFkmkhCa_yfPA2Zg0-xFq_SLDbJTLTHE7uABgOKqv1_8Ko=w@mail.gmail.com> (raw)
In-Reply-To: <875xzbkogr.fsf@linj.tech>
Lin Jian <me@linj.tech> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> Are you sure?
>
> I am no expert of git. So I am not sure.
>
> That being said, have you read those links in my report? My point is
> that the motivation of setting transfer.fsckObjects in [1], i.e.,
> security, is made invalid in [2] because git is secure by default.
> However, related commits are made before (and after) [2].
Yes, I read the links. But I tend to trust the official documentation
more than some random opinions shared online, and the part I quoted says
that this setting _does_ enable some checks that would otherwise not be
done.
next prev parent reply other threads:[~2024-01-30 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 23:16 bug#68810: 29.1; Recommending setting transfer.fsckObjects of git to true is not necessary Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-30 0:39 ` Stefan Kangas
2024-01-30 11:57 ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-30 13:18 ` Eli Zaretskii
2024-01-30 13:53 ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-30 14:22 ` Eli Zaretskii
2024-01-30 20:49 ` Stefan Kangas [this message]
2024-01-30 12:27 ` Eli Zaretskii
2024-01-30 13:48 ` Lin Jian via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkmkhCa_yfPA2Zg0-xFq_SLDbJTLTHE7uABgOKqv1_8Ko=w@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=68810@debbugs.gnu.org \
--cc=me@linj.tech \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.