git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: <git@vger.kernel.org>
Subject: [RFE] Teach hash-object to be able to choose signature types
Date: Fri, 16 Aug 2019 18:22:17 -0400	[thread overview]
Message-ID: <009c01d55481$13d3ce20$3b7b6a60$@nexbridge.com> (raw)

Hi All,

I do not know whether this would be a good enhancement or micro project for
someone (maybe me) to take on, but I'm wondering whether it might be a good
idea to provide an option to hash-object to select the signature being
computed. The use case begins when someone computes an object signature and
stores a pre-converted SHA1 value. Then the repository is changed over to
SHA256. When hash-object is next called, perhaps in a different clone or
some other "next" scenario, the new signature will be SHA256, if I
understand this correctly, and from the perspective of the someone in the
use case, the signature mismatches.

What I am proposing is an option like --signature-type=SHA1|SHA256 or
similar as an option to hash-object to allow the non-default signature to be
selected explicitly. This is not entirely trivial looking through the code
and presumably would require either teaching hash_object_file_literally or
having a separate method to do the alternate calculation.

Thoughts?
Regards,
Randall

-- Brief whoami:
 NonStop developer since approximately 211288444200000000
 UNIX developer since approximately 421664400
-- In my real life, I talk too much.




             reply	other threads:[~2019-08-16 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 22:22 Randall S. Becker [this message]
2019-08-17  1:51 ` [RFE] Teach hash-object to be able to choose signature types brian m. carlson
2019-08-19 17:37   ` Junio C Hamano

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='009c01d55481$13d3ce20$3b7b6a60$@nexbridge.com' \
    --to=rsbecker@nexbridge.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 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).