From: Krzysztof Halasa <khc@pm.waw.pl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: David Lang <david.lang@digitalinsight.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jeff Garzik <jeff@garzik.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Starting to think about sha-256?
Date: Mon, 28 Aug 2006 22:12:54 +0200 [thread overview]
Message-ID: <m34pvwfwl5.fsf@defiant.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0608281034440.27779@g5.osdl.org> (Linus Torvalds's message of "Mon, 28 Aug 2006 10:56:01 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> In related news, the question is what to do about the inadvertent
> collision.. First off, let me remind people that the inadvertent kind
> of collision is really really _really_ damn unlikely, so we'll quite
> likely never ever see it in the full history of the universe.
Actually I think we may see it when somebody tries to put a real
example of conflicting SHA-1 pair into git repository.
--
Krzysztof Halasa
next prev parent reply other threads:[~2006-08-28 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 17:56 Starting to think about sha-256? Jeff Garzik
2006-08-27 20:30 ` Krzysztof Halasa
[not found] ` <Pine.LNX.4.64.0608271343120.27779@g5.o sdl.org>
2006-08-27 20:46 ` Linus Torvalds
2006-08-27 21:14 ` Krzysztof Halasa
2006-08-27 22:02 ` Johannes Schindelin
2006-08-27 22:35 ` Linus Torvalds
2006-08-28 17:27 ` David Lang
2006-08-28 17:56 ` Linus Torvalds
2006-08-28 18:06 ` Linus Torvalds
2006-08-28 18:32 ` Jeff King
2006-08-28 18:46 ` Linus Torvalds
2006-08-28 19:00 ` Jeff King
2006-08-28 20:12 ` Krzysztof Halasa [this message]
2006-08-28 20:20 ` Linus Torvalds
2006-08-28 21:12 ` Krzysztof Halasa
2006-08-28 21:23 ` Linus Torvalds
2006-08-28 23:09 ` Johannes Schindelin
2006-08-28 23:48 ` Linus Torvalds
2006-08-29 6:17 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2006-09-05 9:05 linux
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=m34pvwfwl5.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=Johannes.Schindelin@gmx.de \
--cc=david.lang@digitalinsight.com \
--cc=git@vger.kernel.org \
--cc=jeff@garzik.org \
--cc=torvalds@osdl.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.
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).