unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lin Jian <me@linj.tech>
Cc: stefankangas@gmail.com, 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:18:18 +0200	[thread overview]
Message-ID: <86eddz2c4l.fsf@gnu.org> (raw)
In-Reply-To: <875xzbkogr.fsf@linj.tech> (bug-gnu-emacs@gnu.org)

> Cc: 68810@debbugs.gnu.org
> Date: Tue, 30 Jan 2024 19:57:16 +0800
> From:  Lin Jian via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> 
> 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.

AFAIR, we added that setting because of real problems, not because of
some theoretical concerns.





  reply	other threads:[~2024-01-30 13:18 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86eddz2c4l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68810@debbugs.gnu.org \
    --cc=me@linj.tech \
    --cc=stefankangas@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).