All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Numeric constants as strings
Date: Mon, 19 Feb 2007 01:49:44 -0800	[thread overview]
Message-ID: <7vbqjq8ojr.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200702190916.35813.andyparkins@gmail.com> (Andy Parkins's message of "Mon, 19 Feb 2007 09:16:34 +0000")

Andy Parkins <andyparkins@gmail.com> writes:

> I'm working on bringing my hash width literals patch up to
> date now that 1.5.0 has passed.

I do not want to risk discouraging public discussion on this
topic, but I am not sure if this is really worth it.

It is not like if/when we find SHA-1 is inadequate we would just
switch to SHA-256 and redefine HASH_BYTES from 20 to 32 and be
done with it.  With the need for backward compatibility, we
would probably end up changing "unsigned char sha1[20]" to
something that allows us to tell which hash function's result we
are talking about, like:

	struct {
	       	enum { SHA_1, SHA_256 } type;
               	union {
                        unsigned char sha1[20];
                        unsigned char sha256[32];
		} u;
	};

  parent reply	other threads:[~2007-02-19  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19  9:16 Numeric constants as strings Andy Parkins
2007-02-19  9:38 ` Junio C Hamano
2007-02-19  9:49   ` Shawn O. Pearce
2007-02-19 10:01     ` Matthieu Moy
2007-02-19 10:54       ` Andy Parkins
2007-02-19 10:14   ` Andy Parkins
2007-02-19  9:49 ` Junio C Hamano [this message]
2007-02-19 11:00   ` Andy Parkins
2007-02-19 10:04 ` Mark Wooding
2007-02-19 11:02   ` Andy Parkins
2007-02-20 13:06     ` Jakub Narebski

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=7vbqjq8ojr.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.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 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.