From: Paul Eggert <eggert@cs.ucla.edu>
To: emacs-devel@gnu.org
Subject: Re: Recommend these .gitconfig settings for git integrity.
Date: Tue, 2 Feb 2016 09:54:47 -0800 [thread overview]
Message-ID: <56B0ED67.4030207@cs.ucla.edu> (raw)
In-Reply-To: <loom.20160202T182041-748@post.gmane.org>
On 02/02/2016 09:24 AM, Tom wrote:
> In order to check it the client compares it with something, so it knows
> it received the right thing. I guess the server can also do such a
> comparison,
By then it's too late, if the client omitted the check earlier. The
client can generate commits with valid checksums, commits that contain
data from the unchecked and incorrect commits. It can then send the
commits-with-valid-checksums to the server.
next prev parent reply other threads:[~2016-02-02 17:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 20:22 Recommend these .gitconfig settings for git integrity Karl Fogel
2016-01-31 20:35 ` Eli Zaretskii
2016-01-31 21:37 ` Karl Fogel
2016-01-31 21:48 ` Paul Eggert
2016-02-01 15:42 ` Karl Fogel
2016-02-01 16:01 ` Óscar Fuentes
2016-02-01 16:24 ` Stefan Monnier
2016-02-01 16:39 ` Karl Fogel
2016-02-01 19:12 ` Stefan Monnier
2016-02-01 19:56 ` Paul Eggert
2016-02-01 20:28 ` Eli Zaretskii
2016-02-01 21:40 ` Stefan Monnier
2016-02-02 8:02 ` Paul Eggert
2016-02-02 8:17 ` John Wiegley
2016-02-02 12:58 ` Stefan Monnier
2016-02-02 15:49 ` Óscar Fuentes
2016-02-02 17:55 ` Paul Eggert
2016-02-02 18:48 ` Óscar Fuentes
2016-02-03 7:31 ` Paul Eggert
2016-02-03 16:20 ` Óscar Fuentes
2016-02-03 18:10 ` Paul Eggert
2016-02-03 20:50 ` Óscar Fuentes
2016-02-04 3:53 ` Stefan Monnier
2016-02-02 23:22 ` Karl Fogel
2016-02-03 0:20 ` Lars Ingebrigtsen
2016-02-03 2:16 ` John Wiegley
2016-02-03 2:26 ` Paul Eggert
2016-02-03 6:35 ` John Wiegley
2016-02-03 15:47 ` Eli Zaretskii
2016-02-03 17:40 ` Paul Eggert
2016-02-03 17:52 ` Eli Zaretskii
2016-02-03 18:04 ` Paul Eggert
2016-02-04 0:20 ` Lars Ingebrigtsen
2016-02-02 16:19 ` Eli Zaretskii
2016-02-01 18:39 ` John Wiegley
2016-02-01 16:35 ` Paul Eggert
2016-02-01 16:51 ` Óscar Fuentes
2016-02-01 17:40 ` Paul Eggert
2016-02-01 20:34 ` Óscar Fuentes
2016-02-01 18:09 ` Karl Fogel
2016-02-01 20:56 ` Óscar Fuentes
2016-02-01 21:07 ` Karl Fogel
2016-02-02 10:30 ` Tom
2016-02-02 15:37 ` Paul Eggert
2016-02-02 17:24 ` Tom
2016-02-02 17:54 ` Paul Eggert [this message]
2016-02-01 20:50 ` Karl Fogel
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=56B0ED67.4030207@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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).