From: Bill Zaumen <bill.zaumen@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: "Chris West (Faux)" <faux@goeswhere.com>,
Jeff King <peff@peff.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Suggestion on hashing
Date: Mon, 05 Dec 2011 22:02:27 -0800 [thread overview]
Message-ID: <1323151347.1745.73.camel@yos> (raw)
In-Reply-To: <CACsJy8CM8xqWxTx14QbY+-bT=306p3U=6gJfRaW=dDD-Swo7-w@mail.gmail.com>
On Tue, 2011-12-06 at 11:46 +0700, Nguyen Thai Ngoc Duy wrote:
> On Tue, Dec 6, 2011 at 8:56 AM, Chris West (Faux) <faux@goeswhere.com> wrote:
> >
> > Nguyen Thai Ngoc Duy wrote:
> >>
> >> SHA-1 charateristics (like 20 byte length) are hard coded everywhere
> >> in git, it'd be a big audit.
> >
> >
> > I was planning to look at this anyway. My branch[1] allows
> > init/add/commit with SHA-256, SHA-512 and all the SHA-3 candidates.
>
> Great!
If you are replacing SHA-1 as an object ID with another hash function,
two things to watch are submodules and alternative object databases.
Because of those, it is necessary to worry about the order in which
repositories are converted. In the worst case for submodules, you'd
have to do multiple repositories at the same time, switching between
them depending on what you need at each point.
next prev parent reply other threads:[~2011-12-06 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1322813319.4340.109.camel@yos>
2011-12-02 14:22 ` Suggestion on hashing Nguyen Thai Ngoc Duy
2011-12-02 18:09 ` Jeff King
2011-12-03 0:48 ` Bill Zaumen
2011-12-06 1:56 ` Chris West (Faux)
2011-12-06 3:47 ` Bill Zaumen
2011-12-06 4:46 ` Nguyen Thai Ngoc Duy
2011-12-06 6:02 ` Bill Zaumen [this message]
2011-12-06 6:23 ` Nguyen Thai Ngoc Duy
2011-12-07 1:44 ` Bill Zaumen
2011-12-02 17:54 ` Jeff King
2011-12-03 1:50 ` Bill Zaumen
2011-12-03 15:08 ` Jeff King
2011-12-03 15:34 ` Philip Oakley
2011-12-03 21:21 ` Bill Zaumen
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=1323151347.1745.73.camel@yos \
--to=bill.zaumen@gmail.com \
--cc=faux@goeswhere.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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).