From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: git@vger.kernel.org
Cc: angavrilov@gmail.com, me@yadavpratyush.com,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: [RFC PATCH 0/4] git-gui: support SHA-256 repositories
Date: Mon, 11 Oct 2021 05:17:53 -0700 [thread overview]
Message-ID: <20211011121757.627-1-carenas@gmail.com> (raw)
While poking a SHA-256 hash repository, was surprised to find gitk
would fail with a fatal error when called, hence this series.
Sending as an RFC, since I am not a git-gui or gitk user, and so
while this fixes the original issue and allows me to call gitk to
see the branch merge history (which is usually as much as I do with
it), it is likey missing some changes, as most of them where found
by lightly poking at all of the gui menus (except for remote or tool)
It could also be reordered to reduce unnecessary churn and of course
also needs the gitk change[1] that was sent independently, and better
commit messages.
[1] https://lore.kernel.org/git/20211011114723.204-1-carenas@gmail.com/
Carlo Marcelo Arenas Belón (4):
blame: prefer null_sha1 over nullid and retire later
rename all *_sha1 variables and make null_oid hash aware
expand regexp matching an oid to be hash agnostic
track oid_size to allow for checks that are hash agnostic
git-gui.sh | 30 ++++++++++++++++--------------
lib/blame.tcl | 18 +++++++++---------
lib/checkout_op.tcl | 4 ++--
lib/choose_repository.tcl | 2 +-
lib/commit.tcl | 3 ++-
lib/remote_branch_delete.tcl | 2 +-
6 files changed, 31 insertions(+), 28 deletions(-)
--
2.33.0.1081.g099423f5b7
next reply other threads:[~2021-10-11 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 12:17 Carlo Marcelo Arenas Belón [this message]
2021-10-11 12:17 ` [RFC PATCH 1/4] blame: prefer null_sha1 over nullid and retire later Carlo Marcelo Arenas Belón
2021-10-27 19:43 ` Pratyush Yadav
2021-10-11 12:17 ` [RFC PATCH 2/4] rename all *_sha1 variables and make null_oid hash aware Carlo Marcelo Arenas Belón
2021-10-11 20:07 ` Eric Sunshine
2021-11-13 6:54 ` Pratyush Yadav
2021-10-11 12:17 ` [RFC PATCH 3/4] expand regexp matching an oid to be hash agnostic Carlo Marcelo Arenas Belón
2021-11-13 7:55 ` Pratyush Yadav
2021-10-11 12:17 ` [RFC PATCH 4/4] track oid_size to allow for checks that are " Carlo Marcelo Arenas Belón
2021-11-13 8:04 ` Pratyush Yadav
2021-11-13 8:10 ` Pratyush Yadav
2021-10-11 14:15 ` [RFC PATCH 0/4] git-gui: support SHA-256 repositories Ævar Arnfjörð Bjarmason
2021-10-11 19:47 ` Carlo Arenas
2021-11-13 8:08 ` Pratyush Yadav
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=20211011121757.627-1-carenas@gmail.com \
--to=carenas@gmail.com \
--cc=angavrilov@gmail.com \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.com \
/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).