List for cgit developers and users
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: "nick" <nick@nicholasjohnson.ch>
Cc: <cgit@lists.zx2c4.com>
Subject: Re: Add SHA256 Support
Date: Tue, 17 Oct 2023 09:32:24 +0200	[thread overview]
Message-ID: <20231017093224.4ce4163b@leda.eworm.net> (raw)
In-Reply-To: <CWABSRJPW86V.1589ELRDTB7KP@nicholasjohnson.ch>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

"nick" <nick@nicholasjohnson.ch> on Tue, 2023/10/17 01:33:
> I am a satisfied user of Cgit, but I wish it supported SHA-256 repos.
> 
> Gitea will soon support SHA-256:
> 
> https://github.com/go-gitea/gitea/pull/23894
> 
> There is also at least one repository hosting platform which supports
> SHA-256:
> 
> https://sha2git.com/
> 
> According to Git documentation, it should be safe to implement:
> 
> https://git-scm.com/docs/git-init#Documentation/git-init.txt---object-formatltformatgt
> 
> "Historically, we warned that SHA-256 repositories may later need
> backward incompatible changes when we introduce such interoperability
> features. Today, we only expect compatible changes. Furthermore, if such
> changes prove to be necessary, it can be expected that SHA-256
> repositories created with today’s Git will be usable by future
> versions of Git without data loss."

This is a sha256 repository hosted by cgit:

https://git.zx2c4.com/sha256-oid-test/

Support was added around 2020/10/20.
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2023-10-17  7:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  1:33 nick
2023-10-17  7:32 ` Christian Hesse [this message]

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=20231017093224.4ce4163b@leda.eworm.net \
    --to=list@eworm.de \
    --cc=cgit@lists.zx2c4.com \
    --cc=nick@nicholasjohnson.ch \
    /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).